Comment 0 for bug 2039740

Hi,

Sort of similar to what's reported in LP:1574798. When deploying a bundle, Juju automatically upgrades all the charms, e.g.:

| $ juju deploy --dry-run --verbose ./bundle.yaml
| Located charm "autocert" in charm-hub, channel stable
| Located charm "content-cache" in charm-hub, channel stable
| Located charm "telegraf" in charm-hub, channel candidate
| Changes to deploy bundle:
| - upload charm autocert from charm-hub for series focal from channel stable with architecture=amd64
| - upgrade autocert from charm-hub using charm autocert for series focal from channel stable
| - upload charm content-cache from charm-hub for series focal from channel stable with architecture=amd64
| - upgrade content-cache from charm-hub using charm content-cache for series focal from channel stable
| - expose all endpoints of content-cache and allow access from CIDRs 0.0.0.0/0 and ::/0
| - upload charm telegraf from charm-hub for series focal from channel candidate with architecture=amd64
| - upgrade telegraf from charm-hub using charm telegraf for series focal from channel candidate
| - add relation content-cache - autocert
| - add relation content-cache - telegraf

From the above, we can see that Juju is going to upgrade the various charms (autocert, content-cache, and telegraf). This causes unexpected surprises when all we're trying to do is apply various config changes to a model/environment and ensure the live environment matches what's defined in the bundle. Some charms restart services on charm upgrade (one can argue it's a charm problem).

Would it be possible to have an option to not automatically upgrade charm?

Having an option to disable or not upgrade charm allows us to apply config changes and ensure the live environment matches what's defined in the bundle without any drift and without any surprised outages due to service restarts. This lets the admin decide when to upgrade charms and in sequence without doing them all at once.