-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
CloudMigrations: Break snapshot resources out into their own table #89575
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
mmandrus
added
no-backport
Skip backport of PR
team/operator-experience
no-changelog
Skip including change in changelog/release notes
labels
Jun 21, 2024
PoorlyDefinedBehaviour
approved these changes
Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/backend/db/migration
area/backend
area/frontend
no-backport
Skip backport of PR
no-changelog
Skip including change in changelog/release notes
team/operator-experience
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.
Breaks snapshot results/resources into their own table so that we don't have to store them as a byte array.
Does its best to hide the change from clients using the cloud migration service, by just having snapshot CRUD operations also affect its resources where applicable.
Closes https://github.com/grafana/grafana-operator-experience-squad/issues/827