mirror of https://github.com/ansible/ansible.git
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
49 lines
1.6 KiB
Plaintext
49 lines
1.6 KiB
Plaintext
12 years ago
|
# There is actually no actual shell module source, when you use 'shell' in ansible,
|
||
|
# it runs the 'command' module with special arguments and it behaves differently.
|
||
13 years ago
|
# See the command source and the comment "#USE_SHELL".
|
||
12 years ago
|
|
||
|
DOCUMENTATION = '''
|
||
|
---
|
||
|
module: shell
|
||
|
short_description: Execute commands in nodes.
|
||
|
description:
|
||
12 years ago
|
- The shell module takes the command name followed by a list of arguments,
|
||
|
space delimited. It is almost exactly like the M(command) module but runs
|
||
12 years ago
|
the command through a shell (C(/bin/sh)) on the remote node.
|
||
12 years ago
|
version_added: "0.2"
|
||
12 years ago
|
options:
|
||
|
(free form):
|
||
|
description:
|
||
|
- The command module takes a free form command to run
|
||
|
required: null
|
||
|
default: null
|
||
|
creates:
|
||
|
description:
|
||
|
- a filename, when it already exists, this step will NOT be run
|
||
|
required: false
|
||
|
default: null
|
||
|
chdir:
|
||
|
description:
|
||
12 years ago
|
- cd into this directory before running the command
|
||
12 years ago
|
required: false
|
||
|
default: null
|
||
12 years ago
|
version_added: "0.6"
|
||
12 years ago
|
executable:
|
||
|
description:
|
||
|
- change the shell used to execute the command. Should be an absolute path to the executable.
|
||
|
required: false
|
||
|
default: null
|
||
|
version_added: "0.9"
|
||
12 years ago
|
examples:
|
||
12 years ago
|
- code: "shell: somescript.sh >> somelog.txt"
|
||
12 years ago
|
description: Execute the command in remote shell
|
||
|
notes:
|
||
12 years ago
|
- If you want to execute a command securely and predictably, it may be
|
||
12 years ago
|
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
|
||
|
judgement.
|
||
12 years ago
|
requirements: [ ]
|
||
|
author: Michael DeHaan
|
||
12 years ago
|
'''
|