variable precedence seems not working as intended

Archives Ansible Project
1

From http://docs.ansible.com/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable

If multiple variables of the same name are defined in different places, they win in a certain order, which is:

* -e variables always win
* then comes "most everything else"
* then comes variables defined in inventory
* then comes facts discovered about a system
* then "role defaults", which are the most "defaulty" and lose in priority to everything.

But when I define a variable both in play and in the inventory, the value from the inventory is used.

Bug / docs not up to date / I’m missing something?

2

what version of ansible? I just tested this and play vars override inventory (the one exception is ansible_ vars which are normally used for a particular host’s connection info).

3

version 1.7.2
It was indeed ansible_ssh_user variable. I needed to switch user for one task, but sudo would break ssh agent forwarding.
So this is how it’s supposed to be? Would be nice if docs said something about it…

W dniu piątek, 7 listopada 2014 20:29:59 UTC+1 użytkownik Brian Coca napisał: