John, David, the reason why I'm destroying the service and re-deploy it's because I'm testing/debugging my charm's hooks, specifically the install hook in this case.
My understanding is that 'juju upgrade-charm' will trigger the upgrade-charm hook, right? But I believe the install and upgrade-charm hooks are not always the same, correct? So, in this case using the upgrade option on juju deploy (juju deploy --upgrade --repository /vagrant/charms local:precise/node-app) actually does the job. Thanks for the tips, Daniele On Fri, Dec 6, 2013 at 5:26 PM, David Britton <david.brit...@canonical.com>wrote: > > > On Fri, Dec 6, 2013 at 10:16 AM, John Arbash Meinel < > j...@arbash-meinel.com> wrote: > >> >> You probably want to look at "juju upgrade-charm". When you deploy, we >> take the contents of the local repository and zip it up to store in >> the environment and deploy from there. You need to "upgrade-charm" to >> copy in a new version and tell the system that you want to switch to it. >> >> > Also, if you have destroyed a service, you can't do upgrade-charm, at that > point, you want to make sure your "revision" file in your charm directory > contains a higher number as juju remembers the charms it deploys. The > "--upgrade" flag on juju deploy can automate that for you, in that case. > > See the discussion in this bug, as this behavior surprised me too: > > https://bugs.launchpad.net/juju-core/+bug/1205466 > > -- > David Britton <david.brit...@canonical.com> >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju