Adam, charm revisions turn into a tuple of the charm revision and the revision of each resource provided. This means that if you update the revision of the charm, or any resource, that tuple has been 'upgraded'. So uploading the resource after the fact would trigger upgrade-charm hook and it'll be on the charm author to handle that update. This means things in the install hook need to be able to be run from the upgrade-charm hook.
One thing we've talked about is exposing to the charm author some way to know if a resource is updated so that you only call resource-get and process the file if it's changed. I don't think that's in the current work but something we need to look at providing. On Wed, Feb 17, 2016 at 9:24 AM Adam Collard <adam.coll...@canonical.com> wrote: > Hi Moonstone! > > On Fri, 12 Feb 2016 at 21:27 Katherine Cox-Buday < > katherine.cox-bu...@canonical.com> wrote: > >> Moonstone have been working hard on a new feature coming up in Juju 2.0 >> called "Juju Resources", and we're now at a point where we can share the >> goodness and call for bugs/feedback! As noted in the video linked below, >> the feature isn't quite complete, so expect some rough edges, and for some >> of the CLI details to shift just a bit. >> > > After watching the demo (thanks for sharing!) it struck me that use of the > update-status hook to demonstrate this was pointing to a missing feature > (IMHO). > > Is there a hook that fires when a resource is made available? If I have an > install hook that requires a resource, I could make it transition to > blocked when that resource is missing. But when that resource is provided, > how do I know to try again? > > Thanks, > > Adam > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
