Closed rjhenry closed 5 months ago
Instead of adding a hardcoded environment variable in the Ansible's playbook, I would rather prefer to have a new Ansible var
pip_environment_var
containing a list of environment variables that need to be passed to pip command execution.
I went with minio_pip_environment_vars
, mostly to indicate the scope of the variable in it's name.
Looks like those Molecule tests are a) only warnings and b) also happening on master
now. I suspect something's updated somewhere or similar?
Currently there is an issue, https://github.com/ansible-collections/community.docker/issues/860, making ansible docker package not workig and so "molecule" workflows are broken. There is a molecule, PR https://github.com/ansible/molecule/pull/4185 fixes this issue, so I won`t apply workarround in github actions to avoid installation of the broken package.
Hi @rjhenry, thanks for creating this PR,
Instead of adding a hardcoded environment variable in the Ansible's playbook, I would rather prefer to have a new Ansible var
pip_environment_var
containing a list of environment variables that need to be passed to pip command execution.Could you please update the PR so that generic variable can be used?
Thanks Regards Ricardo