tags 707275 + upstream thanks I'm not 100% sure that this bug shouldn't be set wontfix. There's a balance here to be made between creating an audit trail on the system for what ansible has done to it, and causing too much noise.
It seems to me that erring on the side of logging more audit information is better than the potential for losing the information necessary to figure out what happened if, for example, an ansible playbook play is accidentally spread too wide. Regardless of my own thoughts, upstream has obviously made a decision. My 2c, I think this bug should be moved to an upstream issue for them to put in as a configuration parameter, so users can make their own decision about that balance. Sincerely, Harlan Lieberman-Berg
