Thanks for the example. Would it be crazy/possible to implement optional merging dependent on the hash's name? Seems like for some vars you could possibly want it, in others, not. So things that are in nature restrictive like sudo would be merged, and others wouldn't.
something like: hash_behaviour = replace # by default we replace all vars except those in merge_hashes merge_hashes = foo, baz, bar - James On Wed, Dec 4, 2013 at 7:43 PM, Brian Coca <brianc...@gmail.com> wrote: > group_vars/all: > tomcat_jvm_settings: > - debug=on > - GCfunckymode=True > - dump_heap=true > > group_vars/prod: > tomcat_jvm_settings: > - XmxMax: 234324 > - XmxMin: 12342 > > with merge off, i can use same settings for dev/qa/staging and differnt ones > for prod, if i had merge ON, i would have to always override the settings in > prod: > > - debug=off > - GCfunkymode=False > - dump_heap=true > > > but I think a better example is with user access: > > all: > sudoers: > - devs > - managers > - it > - releng > > staging: > sudoers: > - managers > - releng > - it > > prod: > sudoers: > -it > -releng > > -- > 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 ansible-project+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 ansible-project+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
