I think this could be done a couple different ways too, but there are drawbacks so I didn't try them:
via an entrypoint script to wrap ansible-playbook, where that particular configuration key can be done via ANSIBLE_STRATEGY_PLUGINS="$(find / -type d | grep "ansible_mitogen/plugins" | sort | head -n 1)" ahead of running the ansible-playbook ${@} command
... but that introduces overhead on every invoke, clearly
... and it means that people who manage Windows machines would need a way to disable it (I think)
via using a python venv + requirements.txt in every container to nail down the path precisely across all containers - but I'm not sufficiently python-y to knock that out quickly
I think this could be done a couple different ways too, but there are drawbacks so I didn't try them:
entrypoint
script to wrapansible-playbook
, where that particular configuration key can be done viaANSIBLE_STRATEGY_PLUGINS="$(find / -type d | grep "ansible_mitogen/plugins" | sort | head -n 1)"
ahead of running theansible-playbook ${@}
command