From f0a552c060addd36009e85f39abd29b4e738f1fd Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Fri, 22 Aug 2014 16:12:32 -0400 Subject: [PATCH] Make command warnings off by default to minimize surprises. --- commands/command | 3 +-- commands/shell | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/commands/command b/commands/command index 8071adbc493..c1fabd4f9b4 100644 --- a/commands/command +++ b/commands/command @@ -71,10 +71,9 @@ options: version_added: "1.8" default: yes description: - - "turn off warnings about running a command that is provided by an Ansible module, suggesting you should use that module instead. 'Command warnings' can also be turned off globally in ansible.cfg" + - if command warnings are on in ansible.cfg, do not warn about this particular line if set to no/false. required: false default: True - version_added: "1.5" notes: - If you want to run a command through the shell (say you are using C(<), C(>), C(|), etc), you actually want the M(shell) module instead. The diff --git a/commands/shell b/commands/shell index 7911963e2cb..b63a21080ee 100644 --- a/commands/shell +++ b/commands/shell @@ -43,10 +43,10 @@ options: version_added: "0.9" warn: description: - - turn off warnings about running a command that is provided by an Ansible module. + - if command warnings are on in ansible.cfg, do not warn about this particular line if set to no/false. required: false default: True - version_added: "1.5" + version_added: "1.8" notes: - 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