ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Improve readability, give more info about context

Browse source
This commit is contained in:
Steve Steiner 2016-10-16 11:04:15 -04:00 committed by Brian Coca
parent cf8639ff62
commit 931939e2f8
1 changed files with 6 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
docsite/rst/playbooks_debugger.rst
View file

@ -3,12 +3,10 @@ Playbook Debugger
.. contents:: Topics
In 2.1 we added a ``debug`` strategy. This strategy enables you to invoke a debugger when a task is
failed, and check several info, such as the value of a variable. Also, it is possible to update module
arguments in the debugger, and run the failed task again with new arguments to consider how you
can fix an issue.
In 2.1 we added a ``debug`` strategy. This strategy enables you to invoke a debugger when a task has
failed. You have access to all of the features of the debugger in the context of the failed task. You can then, for example, check or set the value of variables, update module arguments, and re-run the failed task with the new variables and arguments to help resolve the cause of the failure.
To use ``debug`` strategy, change ``strategy`` attribute like this::
To use the ``debug`` strategy, change the ``strategy`` attribute like this::
- hosts: test
strategy: debug
@ -26,8 +24,9 @@ For example, run the playbook below::
- name: wrong variable
ping: data={{ wrong_var }}
The debugger is invoked since *wrong_var* variable is undefined. Let's change the module's args,
and run the task again::
The debugger is invoked since the *wrong_var* variable is undefined.
Let's change the module's arguments and run the task again::
PLAY ***************************************************************************