summaryrefslogtreecommitdiff
path: root/docsite
diff options
context:
space:
mode:
authorbobobox <robincello@gmail.com>2014-10-28 10:15:05 -0500
committerbobobox <robincello@gmail.com>2014-10-28 10:15:05 -0500
commitf38f1c5663d6a5253e30a1e2d84a1596c004f7cd (patch)
treebcef42c32028e930d337a773df1c6e29ca06002c /docsite
parent58defa5cce4ac1095e35a21b167621c27649a34f (diff)
downloadansible-f38f1c5663d6a5253e30a1e2d84a1596c004f7cd.tar.gz
vars_files haven't been discussed yet
I think this is a chapter ordering thing... vars_files have not actually be explained yet (aside from a mention of them in the note right above, which also might need reconsidering?) I think they do get introduced in the next section 'Variables'.
Diffstat (limited to 'docsite')
-rw-r--r--docsite/rst/playbooks_roles.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docsite/rst/playbooks_roles.rst b/docsite/rst/playbooks_roles.rst
index 3a2b2b7514..0d847b3278 100644
--- a/docsite/rst/playbooks_roles.rst
+++ b/docsite/rst/playbooks_roles.rst
@@ -153,7 +153,7 @@ Roles
.. versionadded:: 1.2
-Now that you have learned about :ref:`vars_files <variable_file_separation_details>`, tasks, and handlers, what is the best way to organize your playbooks?
+Now that you have learned about tasks and handlers, what is the best way to organize your playbooks?
The short answer is to use roles! Roles are ways of automatically loading certain vars_files, tasks, and
handlers based on a known file structure. Grouping content by roles also allows easy sharing of roles with other users.