Charm Deployed or Upgrade from Dir Ignores "version"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Nam Nguyen |
Bug Description
As part of the charm build step, if the source directory is under version control, a "version" file is generated as part of the build output.
For charms deployed and upgraded from a charm store, this is included in the archive, is stored in state and is reported as "charm-version" in the output of "juju-status".
This behaviour is consistent when deploying a charm archive. I.e. if one zips the charm source folder including the version file and uses the archive as the path when deploying or upgrading a charm, the charm will report "charm-version".
However, if the source *directory* is used to deploy a local charm, the version file is ignored and the version of the charm is neither stored or reported.
This should be made consistent with the archive behaviour.
Changed in juju: | |
importance: | Undecided → Medium |
milestone: | none → 2.7-beta1 |
status: | New → Triaged |
Changed in juju: | |
assignee: | nobody → Nam Nguyen (nammn) |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To be clear, this is a case where the local charm is used and the deploy command is not issued from the cwd?