Hi Mark, One of the talks that were at our first Ansible meetups here in Berlin was about this very topic more or less. The guys were using an Ansible callback plugin to save the playbook run output in Elasticsearch. I'm not sure if they managed to opensource their work yet but here's another plugin doing that: https://gist.github.com/metmajer/7da2f9599c2d75d80ee5 I wouldn't go for a wrapper. Callback plugins are so much more elegant.
Cheers, Dan. On Wednesday, 29 April 2015 18:14:40 UTC+2, Mark Felder wrote: > > Hello, > > I'm working with ansible in some environments rather sensitive to > security/auditing and we have some significant controls designed around > playbooks working their way up to QA/Prod environments, but our test > environment of course needs to have some looser controls while we work > the kinks out of our playbooks. > > I'm looking for a way to not only log the playbook run itself, but the > entire contents of the playbook so if an event somehow occurs and > something unsavory works its way into the dev environment we can see > what the playbook contents were at the exact time of the playbook run. > > I may also consider settling for good, readable command line output of > exactly what was run; the playbook stdout is simply not sufficient. > > Does anyone have any suggestions on how I could achieve this? > > > Thanks! > -- 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/f5d458c1-175f-4257-9eb3-8399bdc1fb37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
