-
Notifications
You must be signed in to change notification settings - Fork 765
[db_migrator] Add version_202411_02 #3864
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am confused. Why does 202411 branch have a different code for the DB version 202411_01.
I think the version view for a specific DB versions should be same across the branches. Otherwise it not just gets confusing to follow, but could also mean two different things, on same version. When new branches are cut they will have different config migration for the same version. That's not expected?
sonic-utilities/scripts/db_migrator.py
Line 1277 in e6fb8f9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @vaibhavhd ,
I'm not sure I fully understand what you mean.
I didn't change any existing migration logic for version_202411_01.
I only added version_202411_02() to the migration flow so that if config_db.json starts at version_202411_02,
the migrate() function (which uses getattr(self, version)()) can proceed without error.
Could you help clarify your concern and what you'd suggest as the preferred approach in this case?
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am assuming that my question is best answered by @stepanblyschak.
I had it when I check your PR and see difference in version definitions. I think we are missing an enforcement or guideline around this kind of change.
I will sign off on your change as it is not responsible for the confusion that I have.