The context for hooks is not all the same either. What is available for a given hook depends on what the hook itself does. I honestly see no distinction between actions and hooks in practice, and I also don't see how driving that distinction externally would benefit users. I would rather point out that actions are just hooks that are executed when an action is received by the unit. If that's wrong for some reason and there's a relevant distinction, I'd still like to learn why.
On Fri, May 8, 2015 at 1:15 PM, John Weldon <johnweld...@gmail.com> wrote: > > On Fri, May 8, 2015 at 9:13 AM, Gustavo Niemeyer <gust...@niemeyer.net> > wrote: > >> All of that sounds very much in line with what the other hooks do. It's >> still not clear to me why you claim actions and hooks are different. > > > I'm not sure the distinction is important. The key differences are that > hooks have a hook context and actions have an action context, and the > runner for each is different code. > > Cheers, > > -- > John Weldon > -- gustavo @ http://niemeyer.net
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
