chore: Remove repo-upgrade cli command #4124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: tokoko <[email protected]>
jeremyary
approved these changes
May 2, 2024
tmihalac
pushed a commit
to tmihalac/feast
that referenced
this pull request
May 3, 2024
remove repo-upgrade cli command Signed-off-by: tokoko <[email protected]>
tmihalac
pushed a commit
to tmihalac/feast
that referenced
this pull request
May 3, 2024
remove repo-upgrade cli command Signed-off-by: tokoko <[email protected]> Signed-off-by: Theodor Mihalache <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Removes
repo-upgradecli command from feast. The command was supposed to help users rewrite their feature repository codebase (using bowler) when some of feast APIs were dropped/changed in 0.24. We are a long way past that for the command to be of any use. It's mostly just a source of confusion now as an existence of a command namedrepo-upgradeat the first glance implies it needs to be run on every version upgrade.