Those are all good points - but they also seem like implementation details. For example if an action relied on coordination around the leader then the action should be written to protect against that - since it may still break if the user was to run juju run-action myapp/0 && juju run-action myapp/1.
My question is - if I have a model with an application scaled to 10 units, and I know the action is safe to run all the units why do I have to call run-action 10 times, shouldn't I just be able to call it once on the application? Is there a genuine reason we're not supporting this? Cheers Matty On Wed, Aug 3, 2016 at 6:02 PM, Marco Ceppi <[email protected]> wrote: > Because of the ambiguous nature of actions and application. Some would > expect, as you do, to run on all units. Others would expect the leader to > coordinate that action. Furthermore, it becomes more complex as to how > results are curated. Do you get back X UUIDs one for each unit or a single > action UUID but results returned in a different fashion? > > Marco > > On Wed, Aug 3, 2016, 12:35 PM Matthew Williams < > [email protected]> wrote: > >> Hey Folks, >> >> Is there any reason why I can't do juju run-action --application myapp >> (in the same way I can do juju run --application myapp). >> >> Thanks >> >> Matty >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
