# display\_args\_to\_stdout=true - Is it possible to suppress internal args?

**URL:** <https://forum.ansible.com/t/display-args-to-stdout-true-is-it-possible-to-suppress-internal-args/29744>\
**Category:** Ansible Developer\
**Created:** [February 22, 2019, 1:46pm UTC](https://forum.ansible.com/t/display-args-to-stdout-true-is-it-possible-to-suppress-internal-args/29744 "2019-02-22T13:46:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Henning\_Juva](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@Henning\_Juva](https://forum.ansible.com/u/Henning_Juva)\
**Post date:** [February 22, 2019, 1:46pm UTC](https://forum.ansible.com/t/display-args-to-stdout-true-is-it-possible-to-suppress-internal-args/29744/1 "2019-02-22T13:46:16Z")

</div>

I recently upgraded to 2.7.7 from 2.4 and using display\_args\_to\_stdout=true. After upgrade many modules (like stat,command,shell etc) have started including [ansible internal args](https://docs.ansible.com/ansible/latest/dev_guide/developing_program_flow_modules.html#internal-arguments) into what is logged for the task on the command line. Some tasks like yum seems to suppress this behaviour like before. This makes it harder to read and I need to search for the “real” arguments. Is there any way to silence this in ansible.cfg or is this something each module developer need to incorporate?

Example:

TASK [centos : stat \_ansible\_version=2.7.7, \_ansible\_selinux\_special\_fs=[‘fuse’, ‘nfs’, ‘vboxsf’, ‘ramfs’, ‘9p’], \_ansible\_no\_log=False, \_ansible\_module\_name=stat, \_ansible\_debug=False, \_ansible\_verbosity=0, \_ansible\_keep\_remote\_files=False, \_ansible\_syslog\_facility=LOG\_USER, \_ansible\_socket=None, \_ansible\_diff=False, \_ansible\_remote\_tmp=/tmp, \_ansible\_shell\_executable=/bin/sh, path=/tmp, \_ansible\_tmpdir=None, \_ansible\_check\_mode=False] \*\*\*  
ok: [localhost]

TASK [centos : service state=started, enabled=True, name=chronyd] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
ok: [localhost]

Regards,  
Henning

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [March 11, 2019, 10:46pm UTC](https://forum.ansible.com/t/display-args-to-stdout-true-is-it-possible-to-suppress-internal-args/29744/2 "2019-03-11T22:46:57Z")

</div>

no, modules can only return the data, they have no control on display,  
that happens at the callback level.