search

UCL-MIRSG / ansible-collection-infra

Ansible Collection to configure infrastructure for XNAT and OMERO
BSD 3-Clause "New" or "Revised" License
1 stars 0 forks source link

`ansible==10.0.0` breaks the workflows #115

Open paddyroddy opened 1 month ago

paddyroddy commented 1 month ago

Short Description

Not entirely sure what the breakage is, but probably related to https://github.com/UCL-MIRSG/ansible-collection-infra/issues/110. This has been fixed for now with #114 - but ideally we don't want to pin ansible long-term.

Evidence/Steps to Reproduce

Run molecule with ansible>=10.0.0

Acceptance Criteria/Expected Behaviour

No response

Details

No response

Resolution

No response

HChughtai commented 1 month ago

Rather than pinning a specific version, shall we specify that we use a major version and install that - e.g. pip install "ansible==9.x" so that the latest version in that line is used? Then we can have a more considered upgrade to ansible==10.x when we're ready?

HChughtai commented 1 month ago

Ansible 9 will have minor and bugfix releases until Novemeber 2024

And worth looking at the Ansible 10 roadmap to see if any of the breaking changes are relevant to us.

paddyroddy commented 1 month ago

Having discussed this with @HChughtai, think I'm going to change it to ansible_major_version and use the 9.* syntax in the composite action