- 21 Nov, 2012 1 commit
-
-
Jan-Piet Mens committed
-
- 07 Nov, 2012 1 commit
-
-
This makes more sense as there is no purpose in running these remotely.
Dag Wieers committed
-
- 23 Oct, 2012 1 commit
-
-
- added terse syntax to modules.rst - added description of special variables to template module
Jan-Piet Mens committed
-
- 18 Oct, 2012 1 commit
-
-
Fix indent of fail module example to prevent unwanted `<blockquote></pre></p> <br/></blockquote>` from showing up in docsite output.
Luke Antins committed
-
- 12 Oct, 2012 1 commit
-
-
Michael DeHaan committed
-
- 04 Oct, 2012 1 commit
-
-
Dag Wieers committed
-
- 02 Oct, 2012 1 commit
-
-
In some cases you may want to deliberately fail the execution of a playbook. In our provisioning workflow we want to have safeguards in place to avoid provisioning systems that are already in production. Since we reboot physical and virtual systems, it is mandatory we take all the precautions to prevent accidental provisioning. So in our use-case we have the following at the very start of the provisioning playbook: ### Safeguard to protect production systems - local_action: fail msg="System is not ready to be staged according to CMDB" only_if: "'$cmdb_status' != 'to-be-staged'" and we repeat the same task in the (separate included) play that takes care of (re)booting the system using our own boot-media, so that it cannot be accidentally separately run by someone.
Dag Wieers committed
-