ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Fixed documentation in playbooks_variables.rst

Browse source
This commit is contained in:
kustodian 2014-07-18 20:29:25 +02:00
parent cc6ad40534
commit dea19070e2
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docsite/rst/playbooks_variables.rst
View file

@ -1029,7 +1029,7 @@ can set variables in there and make use of them in other roles and elsewhere in
- { role: something_else } - { role: something_else }
.. note:: There are some protections in place to avoid the need to namespace variables. .. note:: There are some protections in place to avoid the need to namespace variables.
In the above, variables defined in common_settings are most definitely available to 'app_user' and 'something_else' tasks, but if In the above, variables defined in common_settings are most definitely available to 'something' and 'something_else' tasks, but if
"something's" guaranteed to have foo set at 12, even if somewhere deep in common settings it set foo to 20. "something's" guaranteed to have foo set at 12, even if somewhere deep in common settings it set foo to 20.
So, that's precedence, explained in a more direct way. Don't worry about precedence, just think about if your role is defining a So, that's precedence, explained in a more direct way. Don't worry about precedence, just think about if your role is defining a