From 8fb14db802ae0d8ac44de4001c2c68f6eac721c6 Mon Sep 17 00:00:00 2001 From: Michael Scherer Date: Sat, 13 Sep 2014 13:25:07 +0200 Subject: [PATCH] Mention defaults subdirectory in a more visible way All examples do not show it, so only someone reading the doc from end to end would know about it. --- docsite/rst/playbooks_best_practices.rst | 2 ++ docsite/rst/playbooks_roles.rst | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docsite/rst/playbooks_best_practices.rst b/docsite/rst/playbooks_best_practices.rst index 7eee9cc68a7..473e20db937 100644 --- a/docsite/rst/playbooks_best_practices.rst +++ b/docsite/rst/playbooks_best_practices.rst @@ -51,6 +51,8 @@ The top level of the directory would contain files and directories like so:: foo.sh # <-- script files for use with the script resource vars/ # main.yml # <-- variables associated with this role + defaults/ # + main.yml # <-- default lower priority variables for this role meta/ # main.yml # <-- role dependencies diff --git a/docsite/rst/playbooks_roles.rst b/docsite/rst/playbooks_roles.rst index eb7b812ea71..fc347e39a01 100644 --- a/docsite/rst/playbooks_roles.rst +++ b/docsite/rst/playbooks_roles.rst @@ -172,6 +172,7 @@ Example project structure:: tasks/ handlers/ vars/ + defaults/ meta/ webservers/ files/ @@ -179,6 +180,7 @@ Example project structure:: tasks/ handlers/ vars/ + defaults/ meta/ In a playbook, it would look like this::