On Fri, Sep 5, 2014 at 1:15 PM, Josh Smift <[email protected]> wrote: > MD> Ansible will print everything, because it's important to know when > MD> things come back. > > In our usage, we frequently don't care at all when things come back: We > have a playbook that we know is going to take several minutes to run > (dozens of tasks on dozens of hosts), so we fire it off, go do something > else, and check back a while later to see what it did. If the recap at the > bottom looks like we expect, that's great; if it doesn't, it'd be really > useful to just see the failures, so we could quickly see what went wrong. >
You might want to consider using Tower. It makes it easy to delve in to specific results and the 2.0 version has a very very nice view for this. You can quickly ignore things you don't care about. CLI output is great -- we don't hamstring it, but somethings are hard to dig through. I do not think making a way to turn off non-changed server info coming back is a good idea - if something didn't come back, you would not easily know. You could also consider using callback plugins to form up your own alternative log. -- 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/CA%2BnsWgxR0izumMtUkSn0mCKfXFxghMK6Zqk5DbYJrr_j%2B%3DsOOg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
