ansible.builtin.raw – Executes a low-down and dirty command

ansible.builtin.raw – Executes a low-down and dirty command

Note

This module is part of ansible-base and included in all Ansible installations. In most cases, you can use the short module name raw even without specifying the collections: keyword. Despite that, we recommend you use the FQCN for easy linking to the module documentation and to avoid conflicting with other collections that may have the same module name.

• Synopsis
• Parameters
• Notes
• See Also
• Examples

Synopsis

• Executes a low-down and dirty SSH command, not going through the module subsystem.
• This is useful and should only be done in a few cases. A common case is installing python on a system without python installed by default. Another is speaking to any devices such as routers that do not have any Python installed. In any other case, using the ansible.builtin.shell or ansible.builtin.command module is much more appropriate.
• Arguments given to raw are run directly through the configured remote shell.
• Standard output, error output and return code are returned when available.
• There is no change handler support for this module.
• This module does not require python on the remote system, much like the ansible.builtin.script module.
• This module is also supported for Windows targets.

Note

This module has a corresponding action plugin.

Parameters

Parameter	Choices/Defaults	Comments
executable string added in 1.0 of ansible.builtin		Change the shell used to execute the command. Should be an absolute path to the executable. When using privilege escalation (become) a default shell will be assigned if one is not provided as privilege escalation requires a shell.
free_form string / required		The raw module takes a free form command to run. There is no parameter actually named 'free form'; see the examples!

Notes

Note

• If using raw from a playbook, you may need to disable fact gathering using gather_facts: no if you’re using raw to bootstrap python onto the machine.
• If you want to execute a command securely and predictably, it may be better to use the ansible.builtin.command or ansible.builtin.shell modules instead.
• The environment keyword does not work with raw normally, it requires a shell which means it only works if executable is set or using the module with privilege escalation (become).
• This module is also supported for Windows targets.

See Also

See also

ansible.builtin.command

The official documentation on the ansible.builtin.command module.

ansible.builtin.shell

The official documentation on the ansible.builtin.shell module.

ansible.windows.win_command

The official documentation on the ansible.windows.win_command module.

ansible.windows.win_shell

The official documentation on the ansible.windows.win_shell module.

Examples

- name: Bootstrap a host without python2 installed
  raw: dnf install -y python2 python2-dnf libselinux-python

- name: Run a command that uses non-posix shell-isms (in this example /bin/sh doesn't handle redirection and wildcards together but bash does)
  raw: cat < /tmp/*txt
  args:
    executable: /bin/bash

- name: Safely use templated variables. Always use quote filter to avoid injection issues.
  raw: "{{ package_mgr|quote }} {{ pkg_flags|quote }} install {{ python|quote }}"

- name: List user accounts on a Windows system
  raw: Get-WmiObject -Class Win32_UserAccount

Authors

• Ansible Core Team
• Michael DeHaan

© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.11/collections/ansible/builtin/raw_module.html