Merge pull request #8196 from kustodian/playbooks_variables.rst
Fixed documentation in playbooks_variables.rst
This commit is contained in:
commit
f0aab114ea
1 changed files with 1 additions and 1 deletions
|
@ -1029,7 +1029,7 @@ can set variables in there and make use of them in other roles and elsewhere in
|
|||
- { role: something_else }
|
||||
|
||||
.. 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.
|
||||
|
||||
So, that's precedence, explained in a more direct way. Don't worry about precedence, just think about if your role is defining a
|
||||
|
|
Loading…
Reference in a new issue