Ahh, ok great :). It does indeed run as your own user when run locally. I should have tried it out first myself! Thanks!
On Friday, 24 March 2017 11:12:54 UTC, R.I.Pienaar wrote: > > hello, > > At present the run_as is a noop, the idea is that there will be a web > service or similar where playbooks live and where you can branch into > other playbooks that might be there too etc. I added the setting because > I want to version the playbooks soon and want these playbooks to be > usable once the service exist. Sorry this was a bit misleading. > > At present - and forever when running locally - it runs as your own > user. > > It would be bad if on your shell some ruby code could just switch you > into another user so on the CLI its always local user. > > Choria has a concept of a 'privileged certificate' that can masquerade > others which is how the webservice will do this. > > > On Fri, Mar 24, 2017, at 12:02, Daniel Sung wrote: > > Choria playbooks need a run_as parameter explicitly set to work. I > > currently have it set to "choria=daniels.mcollective". > > > > Is there a way to have the playbook run as the current user? This would > > be > > useful if I wanted to write a playbook that could be run by multiple > > users. > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups > > "mcollective-users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > > > -- > R.I.Pienaar / www.devco.net / @ripienaar > -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
