Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Migrations: change how resource revisions are exported #6628
Conversation
mjs
added some commits
Nov 29, 2016
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit db9d167
into
juju:develop
Nov 29, 2016
1 check passed
github-check-merge-juju
Built PR, ran unit tests, and tested LXD deploy. Use !!.*!! to request another build. IE, !!build!!, !!retry!!
Details
mjs
deleted the
mjs:MM-resource-format-tweak
branch
Nov 30, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mjs commentedNov 29, 2016
•
Edited 1 time
-
mjs
Nov 29, 2016
Practical testing has shown that exporting resource revisions in a normalised way, as was being done, isn't always going to work. Due to the ability for users to upload resources locally, the details for a given resource revision can vary between charmstore, application and unit.
Charmstore, application and unit resource revisions are now stored separately (much like they are in state). This change touches the model description format and the model export code in state.
QA
Deployed resource using models and manually verified the output of
juju dump-model.