-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible-runner doesn't support ANSIBLE_ENABLE_TASK_DEBUGGER #1327
Comments
ref: ansible/ansible-runner#1327 Signed-off-by: Fabricio Aguiar <[email protected]>
I'm curious why you want to have the task debugger enabled when running playbooks through runner. |
ref: ansible/ansible-runner#1327 Signed-off-by: Fabricio Aguiar <[email protected]>
ref: ansible/ansible-runner#1327 Signed-off-by: Fabricio Aguiar <[email protected]>
ref: ansible/ansible-runner#1327 Signed-off-by: Fabricio Aguiar <[email protected]>
ref: ansible/ansible-runner#1327 Signed-off-by: Fabricio Aguiar <[email protected]>
@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 |
ref: ansible/ansible-runner#1327 Signed-off-by: Fabricio Aguiar <[email protected]>
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/ansible-runner#1327 Signed-off-by: Fabricio Aguiar <[email protected]>
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
![image](https://private-user-images.githubusercontent.com/17153022/284649717-b74efe23-6efb-495d-bd89-7776f5a30735.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwNDA0ODgsIm5iZiI6MTczOTA0MDE4OCwicGF0aCI6Ii8xNzE1MzAyMi8yODQ2NDk3MTctYjc0ZWZlMjMtNmVmYi00OTVkLWJkODktNzc3NmY1YTMwNzM1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDE4NDMwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWEzNWVlNTkzNDNkNjdmNjQxOWQ0ZGIwZmQxYjRkZGIxYTg1NDM5ZTdhNzJkODJhY2Q1YjEzOGYwYmU1MGFlNDQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.giNoIoKSsyklfuXtbgmAreJC7FOkQ-2-sgAJV0oxy_c)
If I run the same playbook with
ansible-playbook
I can see the
![image](https://private-user-images.githubusercontent.com/17153022/284651824-b44b4aeb-8845-4781-909a-55c67572af1d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwNDA0ODgsIm5iZiI6MTczOTA0MDE4OCwicGF0aCI6Ii8xNzE1MzAyMi8yODQ2NTE4MjQtYjQ0YjRhZWItODg0NS00NzgxLTkwOWEtNTVjNjc1NzJhZjFkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDE4NDMwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ5NDA3ZTMzODIzNWFmYjYwMjAyNjlkNjZkYmFhZjYxMjY2Yjc0ZGFiZTQ5Nzg1MTk2NzAzZGM4MDQ5MGM2MTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.B3k9Gblocf2OBYF2eF-9PJ3qnMYYNiQLAw3hIJUWY4s)
(debug)>
promptThe text was updated successfully, but these errors were encountered: