summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSebastian Wiesinger <sebastian@karotte.org>2022-01-18 16:38:34 +0100
committerGitHub <noreply@github.com>2022-01-18 16:38:34 +0100
commit2e0fb34937b66d6976dff4dd514480337b86588e (patch)
tree8de02e9040a6cc99a4bb7ae0f553d83bd55571e1
parentFix unsafe handling of variable PYTHON_BIN (#76767) (diff)
downloadansible-2e0fb34937b66d6976dff4dd514480337b86588e.tar.xz
ansible-2e0fb34937b66d6976dff4dd514480337b86588e.zip
Change "fatal" to "error" in config docs to match actual behaviour (#76760)
-rw-r--r--lib/ansible/config/base.yml2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/ansible/config/base.yml b/lib/ansible/config/base.yml
index b93db4d657..4c6899cc0f 100644
--- a/lib/ansible/config/base.yml
+++ b/lib/ansible/config/base.yml
@@ -225,7 +225,7 @@ COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH:
description:
- When a collection is loaded that does not support the running Ansible version (via the collection metadata key
`requires_ansible`), the default behavior is to issue a warning and continue anyway. Setting this value to `ignore`
- skips the warning entirely, while setting it to `fatal` will immediately halt Ansible execution.
+ skips the warning entirely, while setting it to `error` will immediately halt Ansible execution.
env: [{name: ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH}]
ini: [{key: collections_on_ansible_version_mismatch, section: defaults}]
choices: [error, warning, ignore]