You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
ansible-playbook playbook.yml -K --check -v
Running any playbook with the subcommand results in a densed default output.
ansible-navigator run -m stdout playbook.yml -K --check -v
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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