Hello, thanks for the link. Unfortunately, I am trying to debug the setup module, which is bundled with the app from RedHat. I don't think I would be able to add a breakpoint to that module, least of all on a production system (which, conveniently, is the only place we can replicate this)
Any chance there's a flag I can pass on the command line thats undocumented, that allows me to just turn up the module's verbosity? Or a something that I can add to the top of a playbook to do the same? Or some way to call the setup task (gather_facts: no, create a task that calls setup, and pass it a parameter) that can accomplish this? It seems silly that we can't get more verbosity out of built in modules. I guess each module would have to have an argument added to it to allow for more verbosity? How can I file a bug against the setup module? Thanks again for your help! On Sunday, June 16, 2019 at 4:59:58 PM UTC-5, Kai Stian Olstad wrote: > > On 16.06.2019 22:27, Thomas Spear wrote: > > To be a bit clearer, I want to know if there is some way to run the > setup > > module in debug mode, so I can get more output on what the module is > doing > > as it tries to gather facts from the system. > > https://docs.ansible.com/ansible/latest/dev_guide/debugging.html > > > -- > Kai Stian Olstad > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/027bce36-eb1d-41ab-abd1-fb44235c1330%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
