There is "openstack tripleo config generate ansible" https://opendev.org/openstack/python-tripleoclient/src/branch/master/setup.cfg#L49 interface that relies on GenerateAnsibleConfig and uses tripleo_common.actions.ansible as a shared lib. Historically that lib also was used for generating ansible.cfg for Mistral ansible executions as well.
Since some time ago it seems we've had a discrepancy in configuration methods though. Now we have a second place that ensures ansible.cfg: https://github.com/openstack/python-tripleoclient/blob/master/tripleoclient/utils.py#L611
Those must be unified and not conflict to each other. Otherwise running the aforementioned CLI command by a user overwrites the config generated with the latter code and vice versa.
Since we've switched execution to ansible-runner and removed mistral, we're are doing our best to not use an ansible.cfg file all together. The code within tripleoclient to create an ansible.cfg [0] file, if one doesn't exist, contains only one option; this is the only option not able to be expressed in environment variables [1].
Just as a note, if a user provides an ANSIBLE_CFG file or if one is discovered, we don't replace the file, we simply append the option we require [2]. If you're seeing this method replace a provided ansible.cfg file, not append it, then that is a bug; however, as this stands today it looks like everything is working as intended.
[0] https:/
[1] https:/
[2] https:/