ansible-navigator run does not allow using yaml output about ansible-navigator HOT 3 CLOSED

Navigator does not support use of ANSIBLE_STDOUT_CALLBACK because it needs to know what is the output in order to be able to recognize it and act.

Currently we have no plans to allow use of custom output formats.

from ansible-navigator.

Like @ssbarnea mentioned here, it's really a limitation of how runner need to scrape the stdout from core to create structured data.

One way to work around this might be to use ansible-navigator exec and run ansible-playbook directly. This would land you in the EE and navigator would take care of all the volume mounts for you.

Let us know if that might work.

from ansible-navigator.

Thanks for looking into this.

I experimented with the suggestion and the most efficient command line stanza to solve this would seem to be:

ansible-navigator exec env ANSIBLE_STDOUT_CALLBACK=default ansible-playbook test.yml -i ./inv

Since we always have ANSIBLE_STDOUT_CALLBACK=awx_display set when entering the container we need to override that but since the ansible-navigator exec subcommand will try to exec() something we can't use the regular shell syntax but instead will execute env(1) to set the variable to our liking.

Of course, the above command gets tedious to type after a while so I'm now using this alias:

alias ap='ansible-navigator exec env ANSIBLE_STDOUT_CALLBACK=default ansible-playbook'

And this allows me to run playbooks in EEs using the default callback as if using plain ansible-playbook:

ap test.yml -i ./inv

Thanks!

from ansible-navigator.