We should try to remove the hard-coded ansible_python_interpreter=auto_legacy_silent argument use to force Python 2 usage on the remote host when building the dashboard, database, and reporter AMIs. This should result in Ansible using the Python 3 interpreter it discovers instead.
Motivation
ansible-core 2.17 dropped support for Python 2 and Python 3.6, thus requiring Python 3.7+ on remotes to function. We must pin under this version until we are able to build AMIs using the Python 3 interpreter, which is not ideal in the long term.
I verified that the following Python 2 reliant Ansible roles which are used to build AMIs specify an executable argument with the ansible.builtin.pip module:
🚀 Feature Proposal
We should try to remove the hard-coded
ansible_python_interpreter=auto_legacy_silent
argument use to force Python 2 usage on the remote host when building thedashboard
,database
, andreporter
AMIs. This should result in Ansible using the Python 3 interpreter it discovers instead.Motivation
ansible-core
2.17 dropped support for Python 2 and Python 3.6, thus requiring Python 3.7+ on remotes to function. We must pin under this version until we are able to build AMIs using the Python 3 interpreter, which is not ideal in the long term.