Flag for not capuring stdin neither stdout while running ansible-inventory about ansible HOT 5 CLOSED

Files identified in the description:

• bin/ansible-inventory

If these files are incorrect, please update the component name section of the description or use the component bot command.

from ansible.

This is not really an ansible-inventory issue but how the script inventory plugin works.

from ansible.

Closing as above- if you need to debug a script, just run the script (or better yet: write an inventory plugin and use a debugger).

from ansible.

@nitzmahone I ran the script from command line (./myscript.py) withtout error and could print / breakpoint().
But could not print anything to screen and brakpoint() / pdb.set_trace() would hang if ran from ansible-inventory .

I am not sure whether starting to write my own plugin for debugging purposes on a tool i am still learning would end successfully. Maybe i was not clear enough, thanks for your answer, sorry for the disturbance.

from ansible.

Inventory plugins are far more capable, flexible, and debuggable than inventory scripts in pretty much every way, so especially if you're writing in Python, I'd strongly suggest writing an inventory plugin instead of a script. They don't rely on stdout JSON dumping and have an actual API for interacting with Ansible.

That said, if you really need to debug a Python inventory script, I'd suggest using a debugger that supports debugging subprocesses (eg ipdb, pycharm/pydevd, VSCode). There are ways to get pdb to do that too, but it's a pain.

from ansible.