Closed fao89 closed 12 months ago
I'm curious why you want to have the task debugger enabled when running playbooks through runner.
@sivel to be honest, I never used the debugger. I bumped into this issue because this var was set to true in a sample and I didn't know why my playbook was getting stuck on error. I could only see it once I ran with ansible-playbook
.
I'm going to close this because using the debugger under runner is not a scenario that is ever going to work because of the need for manual interaction with the debugger itself. Runner does not (nor will it ever) have the ability to process manual interaction with Ansible except for very limited ability to recognize and handle password prompts. If you need to use the debugger, you'll have to run ansible-playbook
directly.
https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_debugger.html#enabling-the-debugger-in-configuration-or-an-environment-variable When I set
ANSIBLE_ENABLE_TASK_DEBUGGER=true
and execute my playbook with theansible-runner
:it gets stuck, and it isn't possible to use the debugger
If I run the same playbook with
ansible-playbook
I can see the
(debug)>
prompt