# 1.8 breaks previously documented behaviour of playbook level vars

**URL:** <https://forum.ansible.com/t/1-8-breaks-previously-documented-behaviour-of-playbook-level-vars/17136>\
**Category:** Ansible Developer\
**Created:** [December 23, 2014, 6:28pm UTC](https://forum.ansible.com/t/1-8-breaks-previously-documented-behaviour-of-playbook-level-vars/17136 "2014-12-23T18:28:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Max\_Ivanov](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@Max\_Ivanov](https://forum.ansible.com/u/Max_Ivanov)\
**Post date:** [December 23, 2014, 6:28pm UTC](https://forum.ansible.com/t/1-8-breaks-previously-documented-behaviour-of-playbook-level-vars/17136/1 "2014-12-23T18:28:27Z")

</div>

Hi All,

I am writing regarding the [https://github.com/ansible/ansible/issues/9877](https://github.com/ansible/ansible/issues/9877) where different behaviour of playbook level vars was reported for version 1.8. That issue was closed as not a bug, despite the fact that previous behaviour was clearly documented.

Docs in [http://docs.ansible.com/intro\_inventory.html#splitting-out-host-and-group-specific-data](http://docs.ansible.com/intro_inventory.html#splitting-out-host-and-group-specific-data) explicitly say:

“Tip: In Ansible 1.2 or later the group\_vars/ and host\_vars/ directories can exist in either the playbook directory OR the inventory directory. If both paths exist, variables in the playbook directory will be loaded second.”

but 1.8 version is not following it, it instead prefers variables in “group\_vars” next to playbook over the ones defined in inventory.

The issue is closed as “won’t fix”, therefore I am writing here to discuss this topic. You should not break whay you promised before, guys, you had that feature since 1.2, why did you decide get rid of it now? Lets not discuss how to achieve same result, but to have talk about why working case is being broken?

Thank you.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [December 23, 2014, 7:01pm UTC](https://forum.ansible.com/t/1-8-breaks-previously-documented-behaviour-of-playbook-level-vars/17136/2 "2014-12-23T19:01:39Z")

</div>

Frist, the issue is not closed, much less "won't fix".

Second, "loading second" or last means the playbook vars would  
override the previously defined ones. So group\_vars in playbook  
overriding group\_vars in inventory complies with the documentation.

Third, we are still looking into this (as mentioned above the ticket  
is not closed).

---

<div class="post-metadata">

**Author:** ![Max\_Ivanov](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@Max\_Ivanov](https://forum.ansible.com/u/Max_Ivanov)\
**Post date:** [December 23, 2014, 7:52pm UTC](https://forum.ansible.com/t/1-8-breaks-previously-documented-behaviour-of-playbook-level-vars/17136/3 "2014-12-23T19:52:26Z")

</div>

Hi Brian,

it was closed with an invitation to discuss it in mail list,which I did. It was reopen since almost immediately without me noticing it.

As what "loading second"means, it can be read 2 ways, my understanding was that if it comes second, then it doesn’t touch whatever is already there, therefore it is more defaulty.

I can see that it is only version 1.7.x where playbook level group\_vars are more defaulty, versions 1.6.x and 1.5.x show same behaviour as 1.8.x, it is very unfortunate that I discovered and and start using this feature during 1.7.x cycle.