# Let's default to the YAML stdout callback

**URL:** <https://forum.ansible.com/t/lets-default-to-the-yaml-stdout-callback/27301>\
**Category:** Ansible Developer\
**Created:** [April 17, 2018, 11:39am UTC](https://forum.ansible.com/t/lets-default-to-the-yaml-stdout-callback/27301 "2018-04-17T11:39:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tobias\_Wolf](https://avatars.discourse-cdn.com/v4/letter/t/eada6e/32.png) [@Tobias\_Wolf](https://forum.ansible.com/u/Tobias_Wolf)\
**Post date:** [April 17, 2018, 11:39am UTC](https://forum.ansible.com/t/lets-default-to-the-yaml-stdout-callback/27301/1 "2018-04-17T11:39:13Z")

</div>

I’m writing to suggest to enable YAML’ized output by default.

Ansible 2.5 comes with the new ' **yaml’** callback plugin, which is such a radical usability improvement, that I’m asking myslf, why this is not the default.

The regular callback makes error messages ­— wrapped in a super-long, single-line JSON string — really awkward to read. This is meant for machines, not humans, who are meant to debug these.

The same holds for printed objects, which are suddenly much easier to skim. Also, Ansible never had a proper way of cleanly printing some text for the user. This change would solved that.

Try it using `ANSIBLE_STDOUT_CALLBACK=yaml`

Why make it default? Nobody will find this plugin. In particular newbies. And I would like to be able to use additional callback plugins like “actionable”, and not be forced to choose.

---

<div class="post-metadata">

**Author:** ![Tobias\_Wolf](https://avatars.discourse-cdn.com/v4/letter/t/eada6e/32.png) [@Tobias\_Wolf](https://forum.ansible.com/u/Tobias_Wolf)\
**Post date:** [April 17, 2018, 11:39am UTC](https://forum.ansible.com/t/lets-default-to-the-yaml-stdout-callback/27301/2 "2018-04-17T11:39:55Z")

</div>

Forgot the link, sorry:

[https://docs.ansible.com/ansible/2.5/plugins/callback/yaml.html](https://docs.ansible.com/ansible/2.5/plugins/callback/yaml.html)