a-c-m
/
community.general
mirror of https://github.com/ansible-collections/community.general.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Sphinx/docs syntax fixes

pull/4420/head
Michael DeHaan 2013-07-21 11:18:07 -04:00
parent 10f99938b9
commit 77a4dcca85
2 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docsite/latest/rst/glossary.rst
View File

@ -10,8 +10,7 @@ when a term comes up on the mailing list.
Action Action
++++++ ++++++
An action is a part of a task that specifies which one of the :ref:`modules` will run, and the arguments to pass to that module. Each task can An action is a part of a task that specifies which of the modules to run and the arguments to pass to that module. Each task can have only one action, but it may also have other parameters.
have only one action, but it may also have other parameters.
Ad Hoc Ad Hoc
++++++ ++++++
@ -159,7 +158,7 @@ them in the inventory file. The Host Vars file can also be used to define compl
inventory file. inventory file.
Lazy Evaluation Lazy Evaluation
++++++++++++++ +++++++++++++++
In general, Ansible evaluates any variables in playbook content at the last possible second, which means that if you define a data structure In general, Ansible evaluates any variables in playbook content at the last possible second, which means that if you define a data structure
that data structure itself can define variable values within it, and everything "just works" as you would expect. This also means variable that data structure itself can define variable values within it, and everything "just works" as you would expect. This also means variable

4
docsite/latest/rst/playbooks.rst
View File

@ -541,8 +541,8 @@ If you want to define certain tasks to happen before AND after roles are applied
- shell: echo 'goodbye' - shell: echo 'goodbye'
.. note:: .. note::
If you are using tags with tasks (described later as a means of only running part of a playbook) If using tags with tasks (described later as a means of only running part of a playbook),
be sure you also tag your pre_tasks and post_tasks and pass those along as well, especially if the pre be sure to also tag your pre_tasks and post_tasks and pass those along as well, especially if the pre
and post tasks are used for monitoring outage window control or load balancing. and post tasks are used for monitoring outage window control or load balancing.
Executing A Playbook Executing A Playbook