ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Fixing versionadded fields in the playbook doc

Browse source
This commit is contained in:
James Cammarata 2013-08-23 11:04:06 -05:00
parent 4dc209f731
commit f8a54d162d
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docsite/latest/rst/playbooks.rst
View file

@ -259,7 +259,7 @@ make more sense to break up tasks using the 'include:' directive. We'll show th
Action Shorthand
````````````````
.. versionadded: 0.8
.. versionadded:: 0.8
Ansible prefers listing modules like this in 0.8 and later::
@ -441,7 +441,7 @@ inside another.
Roles
`````
.. versionadded: 1.2
.. 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 ways of automatically loading certain vars_files, tasks, and
@ -549,7 +549,7 @@ If you want to define certain tasks to happen before AND after roles are applied
Role Dependencies
`````````````````
.. versionadded: 1.3
.. versionadded:: 1.3
Role dependencies allow you to automatically pull in other roles when using a role. Role dependencies are stored in the
`meta/main.yml` file contained within the role directory. This file should contain