From 2aba3b4172d4f4ca7dd4cdb0033492beaf246d32 Mon Sep 17 00:00:00 2001 From: Peter Parente Date: Sun, 21 Jun 2015 15:39:22 -0400 Subject: [PATCH] Fix typo: "name" to "role" --- docsite/rst/playbooks_variables.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index b0e2e223cd..7bf006cf75 100644 --- a/docsite/rst/playbooks_variables.rst +++ b/docsite/rst/playbooks_variables.rst @@ -782,7 +782,7 @@ Parameterized roles are useful. If you are using a role and want to override a default, pass it as a parameter to the role like so:: roles: - - { name: apache, http_port: 8080 } + - { role: apache, http_port: 8080 } This makes it clear to the playbook reader that you've made a conscious choice to override some default in the role, or pass in some configuration that the role can't assume by itself. It also allows you to pass something site-specific that isn't really part of the