thanks

sounds like patching "log" is the best way

Am Dienstag, 9. Juni 2015 16:59:55 UTC+2 schrieb Brian Coca:
>
> Ansible already writes to syslog on the target machines also you can 
> turn on a more detail ansible log on the 'master' in ansible.cfg, In 
> general I would advice using a callback that writes to syslog (there 
> is an example in the repo, but it does json/syslog). For your case, if 
> you just want play name and user, it  might be worth patching the 
> existing logging to add that information. 
>
> On Tue, Jun 9, 2015 at 10:53 AM, Jeff Reter <[email protected] 
> <javascript:>> wrote: 
> > logging on server which user, ran which playbook, when 
> > 
> > Am Dienstag, 9. Juni 2015 14:30:08 UTC+2 schrieb Brian Coca: 
> >> 
> >> what are you trying to accomplish? what is this task for? 
> >> 
> >> On Tue, Jun 9, 2015 at 2:44 AM, Jeff Reter <[email protected]> wrote: 
> >> > hmmm, code do no look "read only" 
> >> > 
> >> > and how can add a task, without adding it to >100 playbooks 
> >> > 
> >> > write an own "ansible-playbook" wrapper? 
> >> > 
> >> > is there any better docs than: 
> >> > http://docs.ansible.com/developing_api.html 
> >> > 
> >> > 
> >> > 
> >> > 
> >> > Am Mittwoch, 3. Juni 2015 18:51:30 UTC+2 schrieb Brian Coca: 
> >> >> 
> >> >> callbacks have no influence on playbooks, they are to handle output 
> >> >> from plays/tasks, information only goes in one direction. 
> >> >> 
> >> >> if you need a conditional task, put it int the play 
> >> >> 
> >> >> -- 
> >> >> Brian Coca 
> >> > 
> >> > -- 
> >> > You received this message because you are subscribed to the Google 
> >> > Groups 
> >> > "Ansible Project" group. 
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send 
> >> > an 
> >> > email to [email protected]. 
> >> > To post to this group, send email to [email protected]. 
> >> > To view this discussion on the web visit 
> >> > 
> >> > 
> https://groups.google.com/d/msgid/ansible-project/4565139b-69ad-477a-94ec-abe1e61d791a%40googlegroups.com.
>  
>
> >> > 
> >> > For more options, visit https://groups.google.com/d/optout. 
> >> 
> >> 
> >> 
> >> -- 
> >> Brian Coca 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Ansible Project" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to [email protected] <javascript:>. 
> > To post to this group, send email to [email protected] 
> <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/ansible-project/a9f762e7-d7f0-4dfe-afe9-8c9e8152ab46%40googlegroups.com.
>  
>
> > 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> Brian Coca 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/a091cc2e-3983-44a1-9510-d701f108add8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to