Greetings,
I am trying to understand how (and when) the versions of collections included in the Ansible distro are decided?
We are building our own container image for ansible stuff, and the image is rebuilt nightly. After hitting a bug with the recent ansible 4.1.0 release, we submitted this issue to the community.crypto collection. The bug was fixed extremely fast on Friday, and version 1.7.1 of the collection was released. But still, our image is not updated today?
Our image is installing ansible from PyPi:
python -m pip install -q --no-cache-dir ansible~=${ANSIBLE_VERSION}
I can of course force-install the latest version of the collection into the image (ansible-galaxy collection install community.crypto), but I was expecting bug fixes/patches to be applied by the ansible distro - probably by some included requirements-file.
Any input that can help me understand this would be greatly appreciated!
Regards,
Erik