On Wednesday, 30 April 2014 21:58:45 UTC+1, James Cammarata wrote: > Mark, our main concern was not hiding a warning pertaining to a security > issue, even if there was no current fix available. In order to find some > middle ground, we've gone ahead and added a new configuration option: > system_warnings. In 1.6, just set "system_warnings = False" in your > ansible.cfg and it will suppress these warning messages. > > Thanks! >
Hello James, Should a directory local ansible.cfg propagate to child directories? Only, I've just noticed system_warnings doesn't appear to... https://gist.github.com/phips/443bb40ebeaefc3c654d Is that expected behaviour? Because I really like shipping directory specific ansible.cfg files - handy in given repository. But this means the pycrypto error rears its ugly head as soon as I drop into a child directory. Cheers, Mark -- 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/bbd04b60-72a5-469c-be2f-847a842835c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
