Replies: 2 comments
-
I am also bitten by this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
as a workaround, i just set an environment variable in my ansible-navigator.yml
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When running ansible-playbooks, there is a possibility to format the output in a nice and good readable yaml format using callback plugins.
But it seems stdout_callback is ignored, wen running the ansible-navigator run subcommand instead of ansible-playbook.
You can replicate this behavior using a ansible.cfg like this:
Running any playbook like this results in a nice output as in a yaml file:
Running any playbook with the subcommand results in a densed default output.
In my opinion a nice formating would also be helpful, when running ansible-navigator in mode stdout. What do you think?
Please let me know if i went wrong.
Best regards
fanks4
Beta Was this translation helpful? Give feedback.
All reactions