I’m not much of a python dev, but I do know my way around powershell.
This list is not exhaustive, as there are some “alternative” ENV’s that I excluded just to generate a quick list.
Ansible 2.15.2 2.14.9 lists 189 environment vars with the following powershell snippet:
$ansible_config = ansible-config list -t all --format json | convertfrom-json
$ansible_config.psobject.properties.name| % {$ansible_config.$_.env.name} | sort | uniq
ENV_VARS
ANSIBLE_ACTION_PLUGINS
I’m not sure how to gracefully do this programmatically in AWX where this is would need to be parsed, and I’m not sure that ansible-config is even available in that context.
bcoca
May 21, 2024, 4:34pm
22
try 2.17, I have been improving the output in 2.16 and 2.17 (more complete and more target-able). Also working on adding ‘galaxy servers’ right now (which were left out as they are dynamically generated config)
ansible-config is available in the EE as it is part of the ansible cli, so AWX can test the validity of things for that EE
Actually, that was 2.14.9 native to RHEL 9.3. I forgot to activate my 2.15 venv.
Will build a 2.17 venv and generate another list.
Edit: Eh… Our Nexus pypi cache is stale, don’t even have 2.16 available at the moment.
Ansible 2.15.12 has 193* vars.
ENV_VARS
ANSIBLE_ACTION_PLUGINS
This might be a good time for @AWX to chime in.
bcoca
May 21, 2024, 4:55pm
26
they did already, check above
I meant it would be nice if they could comment specifically in regard to populating a blacklist of ANSIBLE_ environment variables to validate custom credential types against, rather than the ANSIBLE_ prefix itself. And whether or not this would need to be a static list or if it can be generated programmatically from ansible-config on the fly from a control_node’s EE (considering the awx image itself doesn’t have ansible installed as far as I’m aware).
Turns out our mirror wasn’t stale, I just didn’t realize that python3.9 support was dropped in ansible-core>=2.16.
Here’s the environment vars from 2.17, and there doesn’t appear to be any “alternate” values as there were in 2.14. Used the same powershell snippet from above.
196 vars
ENV_VARS
ANSIBLE_ACTION_PLUGINS
I’m still looking forward for @AWX taking part in this discussion.
1 Like
Denney-tech
September 25, 2024, 3:47pm
30
I have a funny feeling that the new credential plugin architecture won’t have this issue. Even if it still does this for “custom credential types” in the UI, you could just go create a named plugin instead. How we go about adding 3rd party plugins is another matter. It may need to be added to the official credential plugins repo until some other installable method becomes available.