4 ms·

Thanks, that setting helps a lot! Whoever prefers configuration files over environment variables can get the same effect by adding to their ~/.ansible.cfg:

• HeadlessChild 5y ago
  One needs to lookout for their config file being overwritten [1] if another ansible.cfg exist. In my case my ~/.ansible.cfg config got overwritten by a local ./ansible.cfg (as per the order the config files are read [2]) in a project directory. In my case I workaround it by _merging_ all potential config files into one at runtime using `crudini` as demonstrated by rsguhr [3]. [1] https://github.com/ansible/proposals/issues/35 https://github.com/ansible/proposals/issues/35 [2] https://docs.ansible.com/ansible/2.4/intro_configuration.html#configuration-file https://docs.ansible.com/ansible/2.4/intro_configuration.htm... [3] https://gitlab.com/-/snippets/1851171 https://gitlab.com/-/snippets/1851171