feat: migrates from 0.6.7 to 1.2.0 #878
Merged
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.
Add database migrations for:
0.6.7
(Jun 16, 2022) ->0.6.8
(Nov 2, 2022):hab_data_rename
(new)0.6.8
(Nov 2, 2022) ->1.0.0
(Mar 31, 2023):add_key_and_reg_state_schemas
(new)1.0.0
(Mar 31, 2023) ->1.2.0
(Oct 4, 2024):rekey_habs
(already existed)I discovered the need for the
hab_data_rename
migration while testing migration for 0.6.7 test Root GAR databases similar to production as we believe v0.6.7 is what is in production for Root GARs.The
add_key_and_reg_state_schemas
we initially thought was specific to Provenant yet in my testing it turns out it is needed to take a Root GAR 0.6.7 database up to 1.0.0, so not specific to Provenant.The
rekey_habs
migration was relabeled from a1.1.0
migration to be a1.2.0
migration since it is not applicable to the1.1.x
branch of releases and only applies to the1.2.0
releases, andmain
, onwards.