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

Merge pull request #2826 from tgerla/devel

Browse source 
Fix up a couple of references to 'only_if' and change them to 'when'
This commit is contained in:
Michael DeHaan 2013-05-02 06:50:22 -07:00
commit 66c52b3308
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -430,7 +430,7 @@ inside another.
this, consider how you can restructure your playbook to be more this, consider how you can restructure your playbook to be more
class/role oriented. This is to say you cannot use a 'fact' to class/role oriented. This is to say you cannot use a 'fact' to
decide what include file to use. All hosts contained within the decide what include file to use. All hosts contained within the
play are going to get the same tasks. ('only_if' provides some play are going to get the same tasks. ('*when*' provides some
ability for hosts to conditionally skip tasks). ability for hosts to conditionally skip tasks).
Roles Roles

4
docsite/latest/rst/playbooks2.rst
View file

@ -288,7 +288,7 @@ there will be accessible to future tasks::
action: site_facts action: site_facts
- action: command echo {{ my_custom_fact_can_be_used_now }} - action: command echo {{ my_custom_fact_can_be_used_now }}
One common useful trick with only_if is to key off the changed result of a last command. As an example:: One common useful trick with *when* is to key off the changed result of a last command. As an example::
tasks: tasks:
- action: template src=/templates/foo.j2 dest=/etc/foo.conf - action: template src=/templates/foo.j2 dest=/etc/foo.conf
@ -700,7 +700,7 @@ Often in a playbook it may be useful to store the result of a given command in a
it later. Use of the command module in this way can in many ways eliminate the need to write site specific facts, for it later. Use of the command module in this way can in many ways eliminate the need to write site specific facts, for
instance, you could test for the existance of a particular program. instance, you could test for the existance of a particular program.
The 'register' keyword decides what variable to save a result in. The resulting variables can be used in templates, action lines, or only_if statements. It looks like this (in an obviously trivial example):: The 'register' keyword decides what variable to save a result in. The resulting variables can be used in templates, action lines, or *when* statements. It looks like this (in an obviously trivial example)::
- name: test play - name: test play
hosts: all hosts: all