|
|
|
@ -58,12 +58,17 @@ The following tasks are illustrative of how filters can be used with conditional
|
|
|
|
- debug: msg="it changed"
|
|
|
|
- debug: msg="it changed"
|
|
|
|
when: result|changed
|
|
|
|
when: result|changed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- debug: msg="it succeeded in Ansible >= 2.1"
|
|
|
|
|
|
|
|
when: result|succeeded
|
|
|
|
|
|
|
|
|
|
|
|
- debug: msg="it succeeded"
|
|
|
|
- debug: msg="it succeeded"
|
|
|
|
when: result|success
|
|
|
|
when: result|success
|
|
|
|
|
|
|
|
|
|
|
|
- debug: msg="it was skipped"
|
|
|
|
- debug: msg="it was skipped"
|
|
|
|
when: result|skipped
|
|
|
|
when: result|skipped
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.. note:: From 2.1 You can also use success, failure, change, skip so the grammer matches, for those that want to be strict about it.
|
|
|
|
|
|
|
|
|
|
|
|
.. _forcing_variables_to_be_defined:
|
|
|
|
.. _forcing_variables_to_be_defined:
|
|
|
|
|
|
|
|
|
|
|
|
Forcing Variables To Be Defined
|
|
|
|
Forcing Variables To Be Defined
|
|
|
|
|