Thanks! In my situations, an inventory variable makes the most sense. For others reference, here is the needed synax in inventory.
[oes10managed:vars] ansible_sudo_flags='-H' Note that the case is lowercase (unlike the environmental variable). This just "grandfathers in" the (newly) broken sudo clients without effecting other clients. I could not get the " -s " flag to work. I received errors like: /bin/sh: /bin/sh: cannot execute binary file Which I take to be further changes in sudo syntax. That said, since I'm running the commands, I'm reasonably happy here that no problematic shell will be triggered. As near as I can tell, this is most likely to avoid malicious playbooks. -- 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/66668c35-fc01-4be2-90ea-4dc6620268ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
