wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Explanation for "check_mode: no" is confusing (#65777)

Browse source 
When an ansible module, e.g., command, does not support check mode, you can use "check_mode: no" in that task to execute the task in normal mode, even when "--check" flag is used. The current document basically says, use "check_mode: no" to run in check mode, which is confusing and inaccurate.
This commit is contained in:
yiskylee 2019-12-12 18:04:57 -05:00 committed by Alicia Cozine
parent f1fc5dba92
commit 1f0b5b09cd
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/docsite/rst/reference_appendices/test_strategies.rst
View file

@ -47,7 +47,7 @@ existing system, using the `--check` flag to the `ansible` command will report i
bring the system into a desired state.
This can let you know up front if there is any need to deploy onto the given system. Ordinarily scripts and commands don't run in check mode, so if you
want certain steps to always execute in check mode, such as calls to the script module, disable check mode for those tasks::
want certain steps to execute in normal mode even when the `--check` flag is used, such as calls to the script module, disable check mode for those tasks::
roles: