From b1ee1a285a6c888fa1a334b60fc4acc2ef86027b Mon Sep 17 00:00:00 2001
From: Brian Coca <bcoca@users.noreply.github.com>
Date: Thu, 7 Jan 2021 15:00:31 -0500
Subject: [PATCH] Added NO_COLOR as config option (#73105)

---
 changelogs/fragments/added_existing_nocolor.yml | 2 ++
 lib/ansible/config/base.yml                     | 6 +++++-
 2 files changed, 7 insertions(+), 1 deletion(-)
 create mode 100644 changelogs/fragments/added_existing_nocolor.yml

diff --git a/changelogs/fragments/added_existing_nocolor.yml b/changelogs/fragments/added_existing_nocolor.yml
new file mode 100644
index 00000000000..481e0f323c9
--- /dev/null
+++ b/changelogs/fragments/added_existing_nocolor.yml
@@ -0,0 +1,2 @@
+minor_changes:
+  - Added NO_COLOR environment var to ansible color configuration, allowing it to integrate with existing convention.
diff --git a/lib/ansible/config/base.yml b/lib/ansible/config/base.yml
index 501492a6fb2..7f36be41df8 100644
--- a/lib/ansible/config/base.yml
+++ b/lib/ansible/config/base.yml
@@ -72,7 +72,11 @@ ANSIBLE_NOCOLOR:
   name: Suppress color output
   default: False
   description: This setting allows suppressing colorizing output, which is used to give a better indication of failure and status information.
-  env: [{name: ANSIBLE_NOCOLOR}]
+  env:
+    - name: ANSIBLE_NOCOLOR
+      # this is generic convention for CLI programs
+    - name: NO_COLOR
+      version_added: '2.11'
   ini:
   - {key: nocolor, section: defaults}
   type: boolean