From 8a860779fdce665f10e208a7f0e9be072029ebd1 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Sat, 11 May 2013 16:40:09 -0400 Subject: [PATCH] Add some notes about 1.2 things, just to make it more obvious. --- docsite/latest/rst/playbooks.rst | 2 ++ docsite/latest/rst/playbooks2.rst | 4 ++++ 2 files changed, 6 insertions(+) diff --git a/docsite/latest/rst/playbooks.rst b/docsite/latest/rst/playbooks.rst index de55bf7f6e5..451950ad30e 100644 --- a/docsite/latest/rst/playbooks.rst +++ b/docsite/latest/rst/playbooks.rst @@ -446,6 +446,8 @@ inside another. Roles ````` +.. versionadded: 1.2 + Now that you have learned about vars_files, tasks, and handlers, what is the best way to organize your playbooks? The short answer is to use roles! Roles are automatic 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. diff --git a/docsite/latest/rst/playbooks2.rst b/docsite/latest/rst/playbooks2.rst index 9f34bdb6e1f..db48b32d72d 100644 --- a/docsite/latest/rst/playbooks2.rst +++ b/docsite/latest/rst/playbooks2.rst @@ -261,6 +261,10 @@ Example:: Conditional Execution ````````````````````` +(Note: this section covers 1.2 conditionals, if you are using a previous version, select +the previous version of the documentation. Those conditional forms continue to be operational +in 1.2, although the new mechanisms are cleaner.) + Sometimes you will want to skip a particular step on a particular host. This could be something as simple as not installing a certain package if the operating system is a particular version, or it could be something like performing some cleanup steps if a filesystem is getting full.