Env vars do not get cleared by rolling update if previously explicitly set

[alicel]

When an Ansible optional config variable is not explicitly set, its corresponding proxy env var is not set and the proxy uses its internal default value for that configuration item.

If the user explicitly sets an optional configuration variable to a certain value and rolls it out as a rolling config update, the new value is correctly set into the corresponding env var of the recreated proxy container. This is the expected behaviour.

However, if the user later unsets that config variable by commenting it out again in the automation and running the rolling update playbook again, the env var of the recreated container still contains the previously explicitly set value, instead of being unset. This is misleading and makes it more difficult for users to try something and then revert to the proxy internal default if they wish to do so.

┆Issue is synchronized with this Jira Task by Unito
┆Components: Automation
┆Priority: Major

[alicel]

These Ansible issues look relevant to this issue: ansible/ansible#31338 and ansible/ansible#31340.