> > We use switch a lot, and customers use this as well. The primary use case > is "I have a bug in production charm that is not available upstream yet". I > expect future 2.0 uses to look like this: > > charm pull <charm> > <hack on code> > juju upgrade-charm --switch ./<charm> <service> > > Another example, esp because of how the charmstore is structured now > > juju deploy trusty/wordpress > # hackity hack > juju deploy --switch cs:~marcoceppi/trusty/wordpress wordpress > > >> >> What would folks lose if --switch were to be dropped for 2.0? Any >> objections to >> doing this? > > > I object. Switch should be updated to support ./local/directory/charm > instead of local: >
Thanks Marco, we'll have to ensure 2.0 is updated to allow --switch with upgrade-charm --path which it currently does not. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
