New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document ansible_group_priority #28777
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -867,6 +867,8 @@ Basically, anything that goes into "role defaults" (the defaults folder inside t | |
If multiple groups have the same variable, the last one loaded wins. | ||
If you define a variable twice in a play's vars: section, the 2nd one wins. | ||
.. note:: the previous describes the default config `hash_behavior=replace`, switch to 'merge' to only partially overwrite. | ||
.. note:: Group loading follows parent/child relationships. Groups of the same 'patent/child' level are then merged following alphabetical order. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. s/patent/parent/ |
||
This last one can be superceeded by the user via `ansible_group_priority`, which defaults to 0 for all groups. | ||
|
||
|
||
Another important thing to consider (for all versions) is that connection variables override config, command line and play/role/task specific options and directives. For example:: | ||
|
@@ -1000,7 +1002,7 @@ can set variables in there and make use of them in other roles and elsewhere in | |
- { role: something, foo: 12 } | ||
- { 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 '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. | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setting [these] controls
=setting the following variables controls
or
the following variables control
(drop "setting")