-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump minimum version of Ansible to 2.7 or greater #242
Comments
Thanks @cognifloyd for the notice and putting it all together! We'll definitely need to do/plan migration to the next major Ansible version. |
Chart updated. 2.9 is out. 2.6 is EOL. |
I would be happy to help with this. I am starting to implement stackstorm for my current employer and I am using Ansible to manage everything. i would be happy to assist with getting these roles up to the latest version |
@setswei Awesome! Pull Requests are welcome! |
I will start working on this and get back to you guys soon. |
I don't think there will be much needed, except to update what the min version required is. |
Ansible 2.5 is EOL as of yesterday (2019-05-16) because 🎉 Ansible
2.82.9 is here.2.8: https://groups.google.com/forum/#!topic/ansible-announce/OmkhL4zN1oo
2.9: https://groups.google.com/forum/#!topic/ansible-announce/chcjYohq6dA
I have not reviewed the ansible-st2 playbooks to see what we can do if we bump the version to 2.6.
2.6 has lots of bugfixes for include* and import*.
2.7 makes using vars with include* and import* more consistent.
2.8 adds support for content collections (repos like this one with more than one role). better jinja defaults if intermediate dict doesn't exist.
2.9 changes loop+var safety handling. ansible-galaxy collections support improvements
Current ansible support matrix for 2.2 and above:
2.9 is out so 2.6 is EOL.
The text was updated successfully, but these errors were encountered: