updated raw docs for environment and executable

it should now reflect how raw works in combination with
become and environment directives
This commit is contained in:
Brian Coca 2016-06-15 11:22:30 -04:00 committed by Matt Clay
parent e7075f3e93
commit 079948eef0

View file

@ -29,6 +29,8 @@ options:
executable: executable:
description: description:
- change the shell used to execute the command. Should be an absolute path to the executable. - change the shell used to execute the command. Should be an absolute path to the executable.
- when using privilege escalation (C(become)), a default shell will be assigned if one is not provided
as privilege escalation requires a shell.
required: false required: false
version_added: "1.0" version_added: "1.0"
description: description:
@ -49,10 +51,10 @@ notes:
using C(gather_facts: no) if you're using C(raw) to bootstrap python using C(gather_facts: no) if you're using C(raw) to bootstrap python
onto the machine." onto the machine."
- If you want to execute a command securely and predictably, it may be - 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 better to use the M(command) or M(shell) modules instead.
playbooks will follow the trend of using M(command) unless M(shell) is - the C(environment) keyword does not work with raw normally, it requires a shell
explicitly required. When running ad-hoc commands, use your best which means it only works if C(executable) is set or using the module
judgement. with privilege escalation (C(become)).
author: author:
- Ansible Core Team - Ansible Core Team
- Michael DeHaan - Michael DeHaan