Mention shell module in command documentation

Users who use the command module for pretty much all shell commands may be stymied when they try using a command with <, >, $VAR, etc., and not know that they can use the `shell` module instead. This documentation fix clarifies this.
pull/5790/head
Jeff Geerling 11 years ago
parent b8d3c0f865
commit bb2cdb11fd

@ -34,7 +34,8 @@ description:
- The M(command) module takes the command name followed by a list of space-delimited arguments. - The M(command) module takes the command name followed by a list of space-delimited arguments.
- The given command will be executed on all selected nodes. It will not be - The given command will be executed on all selected nodes. It will not be
processed through the shell, so variables like C($HOME) and operations processed through the shell, so variables like C($HOME) and operations
like C("<"), C(">"), C("|"), and C("&") will not work. like C("<"), C(">"), C("|"), and C("&") will not work (use the M(shell)
module if you need these features).
options: options:
free_form: free_form:
description: description:

Loading…
Cancel
Save