Getting pure output from Ansible

There are moments when you want Ansible to stop printing anything own and just to show output of the remote command.

Like ssh user@server command, but with all Ansible bells and whistles, with custom ssh arguments, transports, etc, etc.

I’m talking a…


This content originally appeared on DEV Community and was authored by George Shuklin

There are moments when you want Ansible to stop printing anything own and just to show output of the remote command.

Like ssh user@server command, but with all Ansible bells and whistles, with custom ssh arguments, transports, etc, etc.

I'm talking about the ansibile binary, not the ansible-playbook, although, with some tinkering, it's possible to use this trick with ansible-playbook too.

Foundation for tricks:

  1. Use raw module (disaANSIBLE_LOAD_CALLBACK_PLUGINS=1 ANSIBLE_STDOUT_CALLBACK=json ansible -i localhost, -m raw -a 'cat /etc/passwd' all -c local | jq -r '.plays[].tasks[].hosts | to_entries[] | "(.key):\n(.value.stdout)\n"'bles AnsiballZ mechanism)
  2. Use json output (which allow to extract stdout without using unsound grep expressions).
  3. Process it with jq.
  4. Ask jq not to print quotes for string value.

Here it is:

ANSIBLE_LOAD_CALLBACK_PLUGINS=1 \
ANSIBLE_STDOUT_CALLBACK=json \
ansible -i localhost, -m raw -a 'cat /etc/passwd' all -c local \
| jq -r '.plays[].tasks[].hosts[]?.stdout'

Disection:

  1. Env variables says ansible to load callback plugins and to use json callback plugin (output).
  2. -i localhost, and -c local are not important. Use a proper inventory here if you need. localhost here just for an example.
  3. -m raw -a command is usual ansible invocation
  4. -r for jq removes quotes from a string.
  5. Expression .plays[].tasks[].hosts[]?.stdout scans all hosts in all tasks for all plays and prints stdout.

Why do you need it?

Well, the thing I wanted to do was to get a secret file from a remote server and encrypt it locally on the host using sops. I can use community.sops.sops_encrypt module, but it require multiple steps to do, and secrets are nasty to debug, so I don't want to do those steps.

A 'simple' ansible call with | sops -e is require less attention.

But, it requires this 'pristine output' from ansible to avoid mangling the content, so, I had to invent this quirk.


This content originally appeared on DEV Community and was authored by George Shuklin


Print Share Comment Cite Upload Translate Updates
APA

George Shuklin | Sciencx (2025-08-09T13:01:48+00:00) Getting pure output from Ansible. Retrieved from https://www.scien.cx/2025/08/09/getting-pure-output-from-ansible/

MLA
" » Getting pure output from Ansible." George Shuklin | Sciencx - Saturday August 9, 2025, https://www.scien.cx/2025/08/09/getting-pure-output-from-ansible/
HARVARD
George Shuklin | Sciencx Saturday August 9, 2025 » Getting pure output from Ansible., viewed ,<https://www.scien.cx/2025/08/09/getting-pure-output-from-ansible/>
VANCOUVER
George Shuklin | Sciencx - » Getting pure output from Ansible. [Internet]. [Accessed ]. Available from: https://www.scien.cx/2025/08/09/getting-pure-output-from-ansible/
CHICAGO
" » Getting pure output from Ansible." George Shuklin | Sciencx - Accessed . https://www.scien.cx/2025/08/09/getting-pure-output-from-ansible/
IEEE
" » Getting pure output from Ansible." George Shuklin | Sciencx [Online]. Available: https://www.scien.cx/2025/08/09/getting-pure-output-from-ansible/. [Accessed: ]
rf:citation
» Getting pure output from Ansible | George Shuklin | Sciencx | https://www.scien.cx/2025/08/09/getting-pure-output-from-ansible/ |

Please log in to upload a file.



There are no updates yet.
Click the Upload button above to add an update.

You must be logged in to translate posts. Please log in or register.

Related Posts