mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
added clarification on results tests naming
This commit is contained in:
parent
644f0fb190
commit
96495594cc
1 changed files with 7 additions and 0 deletions
|
@ -44,13 +44,20 @@ decide to do something conditionally based on success or failure::
|
|||
- command: /bin/false
|
||||
register: result
|
||||
ignore_errors: True
|
||||
|
||||
- command: /bin/something
|
||||
when: result|failed
|
||||
|
||||
# In older versions of ansible use |success, now both are valid but succedded uses the correct tense.
|
||||
- command: /bin/something_else
|
||||
when: result|succeeded
|
||||
|
||||
- command: /bin/still/something_else
|
||||
when: result|skipped
|
||||
|
||||
|
||||
.. note:: the filters have been updated in 2.1 so both `success` and `succeded` work (`fail`/`failed`, etc).
|
||||
|
||||
Note that was a little bit of foreshadowing on the 'register' statement. We'll get to it a bit later in this chapter.
|
||||
|
||||
As a reminder, to see what facts are available on a particular system, you can do::
|
||||
|
|
Loading…
Reference in a new issue