I think the bug ( feature ) in 1.7.2 was most logically to me. At the moment there is no way to define site-wide defaults value.
Suggestions ? On Monday, January 5, 2015 at 2:58:50 PM UTC+1, James Morgan wrote: > > Noticed this https://github.com/ansible/ansible/issues/9877 though its a > little unclear what the approach should be. > > In my example I can make variable a role default which would fix it though > I need to go and change every instance of this precedence issue. > > The old behaviour seems logical > > On Monday, 5 January 2015 13:43:44 UTC, James Morgan wrote: >> >> Hi, >> >> I am seeing a similar problem with my inventory variables. I have the >> following defined >> >> ./group_vars/all.yml: yum_epel_ansible_managed: *false* >> ./inventory/db-builder/group_vars/all.yml: yum_epel_ansible_managed: >> *true* >> >> Prior to 1.8.1 when running the db-builder inventory this would be >> overridden as *true* >> >> Using 1.8.1 this is now left as *false* >> >> "yum_epel_ansible_managed": "false" >> >> We haven't changed our playbooks or inventories. >> >> This is causing us issues as you'd imagine. Is this approach incorrect as >> it has worked fine previously >> >> Many thanks >> >> James >> > -- 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/9810163f-a21c-469a-8e93-79201ec32b3c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
