BuildTheNet

Opening your workspace

Your learning content and tools are loading.

Learning paths › Automation › Loops, callbacks, strategy and run control

Loops, callbacks, strategy and run control

How a run behaves rather than what it configures: callbacks hooked into play and task events with results sent to a chat channel, a task looped once per item or retried until its condition holds, work restricted by condition, host, tag or limit, the strategy and fork count that stop fast hosts waiting on a slow one, a change predicted without being applied, a task delegated elsewhere or run once — then honest reporting, with failure defined deliberately, change reported truthfully for a read-only command, credentials kept out of logs, a save only when config changed, and a block that recovers through its rescue. Explanation and checks; six written exercises.

Lessons

More in Automation