mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Update playbooks_blocks.rst (#24069)
* Update playbooks_blocks.rst The rescue section documentation should be clear that successful completion of a rescue section will override other error handling behavior. * more precise rescue docs explains in detail the consequences of successful rescue
This commit is contained in:
parent
4291edd820
commit
04bfbb14d6
1 changed files with 2 additions and 1 deletions
|
@ -61,7 +61,8 @@ Blocks also introduce the ability to handle errors in a way similar to exception
|
|||
|
||||
The tasks in the ``block`` would execute normally, if there is any error the ``rescue`` section would get executed
|
||||
with whatever you need to do to recover from the previous error. The ``always`` section runs no matter what previous
|
||||
error did or did not occur in the ``block`` and ``rescue`` sections.
|
||||
error did or did not occur in the ``block`` and ``rescue`` sections. It should be noted that the play continues if a
|
||||
``rescue`` section completes successfully as it 'erases' the error status (but not the reporting), this means it won't trigger ``max_fail_percentage`` nor ``any_errors_fatal`` configurations but will appear in the playbook statistics.
|
||||
|
||||
|
||||
Another example is how to run handlers after an error occurred :
|
||||
|
|
Loading…
Reference in a new issue