On 11/03/16 13:43, Rick Harding wrote: > The one use case that came up just this week is the ability to crosscrade > from different channels of charms in the new charm publishing world. You > deploy the charm from the stable path. > > You find a bug, and the charm author tests a fix and publishes it to the > development channel. The author then reaches out to you to test the fix. > You could use upgrade-charm to switch tracking the stable channel to the > development channel and back. > > I think it's typically used to move a running deployment to a fork of a > charm that is either maintained, has a bugfix you want, or other such > reasons. > > I think we want to keep it. Can we make it safer? Provider better docs? I > think so, but I don't think we can remove it. >
Ok, thanks for clarifying. The help text was a little confusing because it mentioned switch in the same breath as local repos. The command does check that the new charm declares the same relations and has the same config schema etc. -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
