feature request: renaming charms without breaking upgrades
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Snap Store Server |
New
|
Undecided
|
Unassigned |
Bug Description
This is a feature request for the ability to be able to rename charms without requiring charm operators to switch to the newly named charm to continue to receive charm updates.
The specific use case we have in mind is for https:/
Expected workflow:
* We rename the charm from ubuntu-advantage to ubuntu-pro, and publish it at https:/
* Visiting https:/
* If you've deployed "ubuntu-advantage" and run "juju refresh ubuntu-advantage" you'd get the charm that's been published as ubuntu-pro.
* If you run `juju deploy ubuntu-advantage" you get the charm that's been published as "ubuntu-pro".
tags: | added: canonical-is |
Changed in juju: | |
assignee: | nobody → Heather Lanigan (hmlanigan) |
Changed in juju: | |
importance: | Undecided → Wishlist |
assignee: | Heather Lanigan (hmlanigan) → nobody |
Changed in juju: | |
status: | Incomplete → Triaged |
Part of this request has already been implemented in juju, though we do no have an example to test with.
Once a charm is deployed by name, juju communicates with charmhub via a unique ID, provided by charmhub, in anticipation of this scenario.
Juju currently does not have the ability to rename an application if that is required.
Being able to run `juju deploy ubuntu-advantage` and get `ubuntu-pro` is a feature request for charmhub, added snap store server to address.