feat: add database migrations up to 1.2.0 #874
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
kentbull
force-pushed
the
add-migration-support-and-2022-10-05-hab-migration
branch
4 times, most recently
from
c9216ca
to
c5319af
Compare
kentbull
force-pushed
the
add-migration-support-and-2022-10-05-hab-migration
branch
from
c5319af
to
eab003f
Compare
|
This includes the semver cleanup idea from #872 |
including database migrations for 0.6.7 (None) -> 0.6.8, 0.6.8 -> 1.0.0, 1.0.0 -> 1.2.0
kentbull
force-pushed
the
add-migration-support-and-2022-10-05-hab-migration
branch
from
eab003f
to
d972a24
Compare
pfeairheller
approved these changes
Oct 11, 2024
pfeairheller
deleted the
add-migration-support-and-2022-10-05-hab-migration
branch
kentbull
added a commit
to kentbull/keripy
that referenced
this pull request
Oct 14, 2024
including database migrations for 0.6.7 (None) -> 0.6.8, 0.6.8 -> 1.0.0, 1.0.0 -> 1.2.0
pfeairheller
pushed a commit
that referenced
this pull request
Oct 24, 2024
* feat: add database migrations up to 1.2.0 (#874) including database migrations for 0.6.7 (None) -> 0.6.8, 0.6.8 -> 1.0.0, 1.0.0 -> 1.2.0 * fix: preserve name from 0.6.7 -> 0.6.8 * chore: remove unused db in 1.1.x releases
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.
Adds 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_renamemigration 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_schemaswe 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.I added the
name,base, andtempargs todb.migrate(...)so that theviring.Regerdatabase could be initialized without having to open up theHabery.Important
The
rekey_habsmigration is not run even though it is included in this PR because it's version of1.2.0is above the KERI version of1.1.19stated in KERIpy. That migration is only needed for thev1.2.xseries of releases. I include it in this PR only for completeness to remove any question of whether it is needed or not. It's not needed, though it is useful to see in this PR for reference.