From 18f4f0549faabefbd0457cde0dd86b0d0fed406b Mon Sep 17 00:00:00 2001 From: Marek Czernek Date: Mon, 28 Oct 2019 21:01:10 +0100 Subject: [PATCH] Correct a typo (#64020) --- docs/docsite/rst/user_guide/playbooks_variables.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/user_guide/playbooks_variables.rst b/docs/docsite/rst/user_guide/playbooks_variables.rst index b5dd80788bb..d099a52d4c0 100644 --- a/docs/docsite/rst/user_guide/playbooks_variables.rst +++ b/docs/docsite/rst/user_guide/playbooks_variables.rst @@ -1044,7 +1044,7 @@ Basically, anything that goes into "role defaults" (the defaults folder inside t If you define a variable twice in a play's ``vars:`` section, the second one wins. .. note:: The previous describes the default config ``hash_behaviour=replace``, switch to ``merge`` to only partially overwrite. .. note:: Group loading follows parent/child relationships. Groups of the same 'parent/child' level are then merged following alphabetical order. - This last one can be superceeded by the user via ``ansible_group_priority``, which defaults to ``1`` for all groups. + This last one can be superseded by the user via ``ansible_group_priority``, which defaults to ``1`` for all groups. This variable, ``ansible_group_priority``, can only be set in the inventory source and not in group_vars/ as the variable is used in the loading of group_vars/. Another important thing to consider (for all versions) is that connection variables override config, command line and play/role/task specific options and keywords. See :ref:`general_precedence_rules` for more details. For example, if your inventory specifies ``ansible_user: ramon`` and you run::