"local" charm schema should allow deploying previously deployed local charms
Bug #1611514 reported by
Katherine Cox-Buday
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Katherine Cox-Buday |
Bug Description
As part of the work to make deploying local charms easier, we removed the "local:" schema in favor of relative-path notation (e.g. juju deploy ./foo) and declaring the supported series in metadata.yaml.
However, we still store local charms in Juju's database using the "local:" notation.
We should re-enable utilizing the "local:" schema when deploying charms, but change the meaning to be "deploy this charm which should already exist in the controller".
Changed in juju-core: | |
status: | New → In Progress |
Changed in juju-core: | |
milestone: | none → 2.0-beta16 |
importance: | Undecided → High |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta16 → none |
milestone: | none → 2.0-beta16 |
tags: | added: blocker |
Changed in juju: | |
importance: | High → Critical |
Changed in juju: | |
milestone: | 2.0-beta16 → 2.0-beta17 |
Changed in juju: | |
status: | In Progress → Fix Committed |
tags: | removed: blocker |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Will this change allow me to upload a charm to a model and then deploy it via the api using a 'local:' charm-url?