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://charmhub.io/ubuntu-advantage. Most likely this charm needs to be renamed to "ubuntu-pro" (we'll confirm this with the relevant product team). But this is a charm we install on every VM, so it will be somewhat painful to handle charm upgrades. Also, someone outside of Canonical who has installed this charm would have no way of knowing that a "juju refresh ubuntu-advantage" is finding no updates because we've renamed the charm to "ubuntu-pro".
Expected workflow:
* We rename the charm from ubuntu-advantage to ubuntu-pro, and publish it at https://charmhub.io/ubuntu-pro.
* Visiting https://charmhub.io/ubuntu-advantage redirects you to https://charmhub.io/ubuntu-pro.
* 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".
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.