Add some notes about 1.2 things, just to make it more obvious.

This commit is contained in:
Michael DeHaan 2013-05-11 16:40:09 -04:00
parent 25d5018f75
commit 8a860779fd
2 changed files with 6 additions and 0 deletions

View file

@ -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.

View file

@ -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.