From 8d37c6f091579313dc3e44dbe16adc69c2c23056 Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Fri, 14 Nov 2014 16:20:52 -0500 Subject: [PATCH] minor clarifications of variable precedence --- docsite/rst/playbooks_variables.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index 738148106b4..34d5a77be41 100644 --- a/docsite/rst/playbooks_variables.rst +++ b/docsite/rst/playbooks_variables.rst @@ -955,9 +955,10 @@ a use for it. 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 + * extra vars (-e in the command line) always win + * then comes connection variables defined in inventory (ansible_ssh_user, etc) + * then comes "most everything else" (command line switches, vars in play, included vars, etc) + * then comes the rest of the 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.