Sorry, not following you. In this example I'm not storing any vars in playbooks.
I find it strange that group-specific vars at env/dev/group_vars/node override group_vars/all, but env/dev/group_vars/all does not. It sounds like that's expected, so it's not a bug, but I don't understand the logic behind it. An example of a var I'd like defined as a default but may want to override on a per-environment basis is version. Let's say I want my default to be 0.9.0, but in production I want to override the default and specify 0.8.0. On Tuesday, December 16, 2014 2:32:37 PM UTC-7, Brian Coca wrote: > > No, the play specific group_vars is there for overriding inventory > group_vars, this works as designed. > > In general inventory is something you normally share across projects, > plays are more specific to the action you want to accomplish, this is > the logic followed for the above behavior. > -- > Brian Coca > -- 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/a3eb92a6-eeca-487c-80d1-812a3b374040%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
