mirror of
https://github.com/ansible-collections/community.general.git
synced 2026-05-06 13:22:48 +00:00
Jumbo DOCUMENTATION patch
This commit is contained in:
@@ -7,8 +7,10 @@ DOCUMENTATION = '''
|
||||
module: shell
|
||||
short_description: Execute commands in nodes.
|
||||
description:
|
||||
- The shell module takes the command name followed by a list of arguments, space delimited. It is almost exactly like the command module but runs the command through the user's configured shell on the remote node.
|
||||
version_added: "0.0.2"
|
||||
- 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
|
||||
the command through the user's configured shell on the remote node.
|
||||
version_added: "0.2"
|
||||
options:
|
||||
(free form):
|
||||
description:
|
||||
@@ -29,7 +31,11 @@ examples:
|
||||
- code: shell somescript.sh >> somelog.txt
|
||||
description: Execute the command in remote shell
|
||||
notes:
|
||||
- If you want to execute a command securely and predicably, it may be better to use the '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.
|
||||
- If you want to execute a command securely and predicably, 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
|
||||
judgement.
|
||||
requirements: [ ]
|
||||
author: Michael DeHaan
|
||||
'''
|
||||
'''
|
||||
|
||||
Reference in New Issue
Block a user