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
Fix the series selection logic for deploying local charms. #7285
Conversation
// | ||
// This type should really have a Validate method, as the force flag | ||
// is really only valid if the seriesFlag is specified. | ||
// There is code and tests that allow the force flag when series isn't |
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.
Can we make this a TODO.
Bonus points for a tech-debt bug.
96306dc
to
7ddc8fb
Compare
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Build failed: Tests failed |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Build failed: Tests failed |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Build failed: Tests failed |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Description of change
There was incorrect logic around old style local charms and the series that should be used by default.
The seriesSelector object now holds all that logic. Precedence is as follows:
QA steps
This will fix our CI test failures where they are deploying an old style charm with no series specified in the metadata.