Add example of using non-posix shellisms to raw and shell

Fixes #14262
This commit is contained in:
Toshio Kuratomi 2016-02-03 13:07:30 -08:00 committed by Matt Clay
parent c87f70429b
commit 697980d7cc
2 changed files with 19 additions and 1 deletions

View file

@ -45,7 +45,10 @@ description:
- This module does not require python on the remote system, much like
the M(script) module.
notes:
- If you want to execute a command securely and predictably, it may be
- "If using raw from a playbook, you may need to disable fact gathering
using C(gather_facts: no) if you're using C(raw) to bootstrap python
onto the machine."
- If you want to execute a command securely and predictably, it may be
better to use the M(command) module instead. Best practices when writing
playbooks will follow the trend of using M(command) unless M(shell) is
explicitly required. When running ad-hoc commands, use your best
@ -58,4 +61,13 @@ author:
EXAMPLES = '''
# Bootstrap a legacy python 2.4 host
- raw: yum -y install python-simplejson
# Bootstrap a host without python2 installed
- raw: dnf install -y python2 python2-dnf libselinux-python
# 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
'''

View file

@ -92,4 +92,10 @@ EXAMPLES = '''
args:
chdir: somedir/
creates: somelog.txt
# Run a command that uses non-posix shell-isms (in this example /bin/sh
# doesn't handle redirection and wildcards together but bash does)
- shell: cat < /tmp/*txt
args:
executable: /bin/bash
'''