Callbacks are a good way to handle it. I had a callback that tracked that and summarized at the end.
I ended up removing that portion of the code before it hit our git repo, but it was pretty easy to implement. On Friday, January 17, 2014, Brian Coca <[email protected]> wrote: > I use the logfile callback plugin and just look at ~/ansible.log > > > -- > Brian Coca > Stultorum infinitus est numerus > > 0110000101110010011001010110111000100111011101000010000001111001011011110111010100100000011100110110110101100001011100100111010000100001 > Pedo mellon a minno > > -- > 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:_e({}, > 'cvml', 'ansible-project%[email protected]');>. > To post to this group, send email to > [email protected]<javascript:_e({}, 'cvml', > '[email protected]');> > . > For more options, visit https://groups.google.com/groups/opt_out. > -- Matt Martz [email protected] http://sivel.net/ -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
