You are reading an unmaintained version of the Ansible documentation. Unmaintained Ansible versions can contain unfixed security vulnerabilities (CVE). Please upgrade to a maintained version. See the latest Ansible documentation.
Executes a low-down and dirty SSH command, not going through the module subsystem. This is useful and should only be done in two cases. The first case is installing python-simplejson on older (Python 2.4 and before) hosts that need it as a dependency to run modules, since nearly all core modules require it. Another is speaking to any devices such as routers that do not have any Python installed. In any other case, using the shell or 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 script module.
This module is also supported for Windows targets.
-name:Bootstrap a legacy python 2.4 hostraw:yum -y install python-simplejson-name:Bootstrap a host without python2 installedraw: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/*txtargs: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_simplejson|quote}}"
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 command or 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.
This module is flagged as stableinterface which means that the maintainers for this module guarantee that no backward incompatible interface changes will be made.
For more information about Red Hat’s this support of this module, please
refer to this knowledge base article<https://access.redhat.com/articles/rhel-top-support-policies>