Chapter 4. Controlling Task Conditions
Ansible fundamentally operates on the concept of task statuses: Ok, Changed, Failed, or Skipped. These statuses determine whether any further tasks should be executed on a host, and whether handlers should be notified due of any changes. Tasks can also make use of conditionals that check the status of previous tasks to control operation.
In this chapter, we'll explore ways to influence Ansible when determining the task status:
- Controlling what defines a failure
- Controlling what defines a change
Defining a failure
Most modules that ship with Ansible have an opinion on what constitutes an error. An error condition is highly dependent upon the module and what the module is attempting to accomplish. When a module ...
Get Mastering Ansible now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
