Actions will not be using SSH to get to the machines; they'll be integrated into the model. We hope to retire the direct-SSH implementation of juju run so as to allow the same functionality via an implicit action, but we're not worrying about that until we have the actions infrastructure in place.
Independent of juju run, I wouldn't *encourage* the use of arbitrary code, but I can't see any sane way to prevent charm authors from defining an action that accepted arbitrary code as a parameter -- and it's indeed likely that we'll end up considering juju run to be literally an action that accepts arbitrary code. We will of course need to exercise care wrt permissions: the ability to execute juju run is clearly essentially equivalent to the ability to ssh and hence execute arbitrary code. Cheers William On Thu, May 15, 2014 at 1:13 AM, Mike Sam <[email protected]> wrote: > I know juju run is out but I am wondering when we should expect Actions > that do not require ssh access to the machines? > > Also, will actions allow arbitrary (defined at runtime) hook code or show > the code be part of the charm already? > > Thanks, > Mike > > -- > 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
