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.
(This is for things like system configuration management, the "make sure
everything on this system is configured like it's supposed to be" sort of
playbook.)
-Josh ([email protected])
This email is intended for the person(s) to whom it is addressed and may
contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use,
distribution, copying, or disclosure by any person other than the addressee(s)
is strictly prohibited. If you have received this email in error, please notify
the sender immediately by return email and delete the message and any
attachments from your system.
--
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/21513.61363.624666.761496%40gargle.gargle.HOWL.
For more options, visit https://groups.google.com/d/optout.
