The config documentation was suggesting that most people leave it in the standard mode to make sure everybody's writing playbooks the same way.
That was it. On Mon, Dec 2, 2013 at 2:50 AM, Serge van Ginderachter < [email protected]> wrote: > > On 2 December 2013 02:32, Eric Chaves <[email protected]> wrote: > >> after reading the ansible.cfg documentation page, I found the parameter >> you mentioned, together with an warning against it. Since I value the >> experience from everyone here more than mine, would you care to explain why >> merging the hashes could be such bad idea? > > > I'm not sure which warning that is, but I can confirm you I have been > using the merge functionality for a long time, and do not experience any > problems with it. > > Of course you have to remember or take into account where you define > (different parts of) those hashes, and understand the possible implications. > > Serge > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
