Permalink
Please sign in to comment.
Browse files
upgrade-charm now allows upgrading local charms
This fixes lp:1609463. In the event that we try and add a local charm, to verify we're upgrading the same charm, we check whether the application names are the same. We were incorrectly checking the argument to `--path` as the charm name and not the application name in the metadata.yaml. This was an implicit assumption that the path reflects the application name (not always true). There are also some very minor drive-by clean-ups in our Sisyphusian effort to converge towards a better codebase. Further clean-ups in this area are possible; namely: - Passing in an `UpgradeCharmAPI` type and using it throughout. - There is commonality between `deploy` and `upgrade-charm` in resolving arguments and doing something useful with them. There is an opportunity to create a component and to pass it into both commands.
- Loading branch information...
Showing
with
78 additions
and 46 deletions.
0 comments on commit
51d6437