updog: move migration searching code to update_metadata for reuse #920
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.
Issue number:
Supports #905 and #91
Description of changes:
Both migrator and updog will need to determine what migrations to use by parsing the manifest. Both will also need to load the manifest from a
tough::Repository.As a warm-up for signed migrations, this PR moves such logic from updog to update_metadata. update_metadata will be used by both migrator and updog so that they can share such code. Also, to do this, the tiny dependency update_metadata had on migrator has been inverted.
Testing done:
cargo make,cargo test, and an upgrade/downgrade test.Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.