Narrow proxy_env scope.

[Hiroaki KAWAI (hkwi)]

Description

When using ansible proxy_env to set environment variables, they end up being applied even to internal connectivity checks between components, which can cause those checks to fail.

This typically happens in environments where the proxy cannot directly connect to the target host, for example in lab setups behind NAT.

System default yum repositories might be pre-configured to use proxy, because Confluent yum repository will be registered with proxy statically by default in the playbook run.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

With a set of virtual hosts in a single physical host, where external proxy is required to connect to the Internet.

Checklist:

• Any variable/code changes have been validated to be backwards compatible (doesn't break upgrade)
• I have added tests that prove my fix is effective or that my feature works
• If required, I have ensured the changes can be discovered by cp-ansible discovery codebase
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules