fix: Wrong password limit in container registry migration script
#2986
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
github-actions
bot
added
comp:manager
jopemachine
changed the title
password limit in container registry migration script
lablup-octodog
pushed a commit
that referenced
this pull request
Oct 28, 2024
…2986) Backported-from: main (24.12) Backported-to: 24.09 Backport-of: 2986
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.
Hotfix of #1917 migration script.
Remove the incorrect length restriction applied to the password field in the existing migration script.
Caution
This PR contains updates to a revision script which has already been published to the stable release. Existing clusters operating Backend.AI 24.09 should execute following script to manually elaborate the database schema:
During the process, data inserted to the
container_registries.extracolumn will be wiped out. The column is effective only for AWS ECR, GitLab and GitHub registries; you may safely ignore this warning if you are not engaged with those registries.Checklist: (if applicable)