-
Notifications
You must be signed in to change notification settings - Fork 519
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
Add 'set-migrations' subcommand to updata #756
Conversation
@@ -80,6 +80,14 @@ pub struct Manifest { | |||
pub datastore_versions: BTreeMap<SemVer, DataVersion>, | |||
} | |||
|
|||
#[derive(Debug, Default, Serialize, Deserialize)] | |||
pub struct Release { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really keen on having this struct here, but it represents the best and easiest place to deal with ser/deserializing Release.toml
data for now.
As we do a few more releases and get a better idea of how we're going to use this data I think it will move. But short-term, this will do the job.
This commit adds a 'set-migrations' subcommand to updata that will copy the migrations section from a file to another file. This subcommand replaces the `add-migration` and `remove-migration` subcommands. It is meant to be used to take migrations data from `Release.toml` and copy it to `manifest.json`.
e6707d1
to
f0b614d
Compare
Add comment suggested by @tjkirch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐶
Issue number:
N/A
Description of changes:
This commit adds a 'set-migrations' subcommand to updata that will
copy the migrations section from a file to another file. This
subcommand replaces the
add-migration
andremove-migration
subcommands. It is meant to be used to take migrations data from
Release.toml
and copy it tomanifest.json
.Testing done:
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.