Hi, Thanks for the reply. Out of interest do you know the rationale for having inventory related vars having less precedence than playbook. I think this is where our problems lie. We have quite a few different types of deployments for different envs. Different box layout configurations etc. Single box / flat tier on local VMs through to 3 tier many box EC2 environments.
I do use overarching groups (groups of groups) to tailor these different environments but occasionally need to tweak certain hosts. This I would like to happen in the inventory as it isolates the change without needing to add lots of playbook level group/hostvars. Though I can't override at the inventory level with the current precedence. To achieve this I need to knock the var out of the playbook level group and define in each inventory, which leads to duplication. I guess its just a case of re-thinking the grouping and specifying more playbook level groups. Sorry for waffling on. I want to try and follow common best practices for laying things out. I just want to try and reduce duplication as much as possible as it causes all manner of problems. Thanks On Thursday, 22 October 2015 04:35:22 UTC+1, Brian Coca wrote: > > group_vars/all still has less precedence than other groups > > > -- > 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/d88edb9b-f359-4d9f-a2fd-2e615cb3549e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
