-
Notifications
You must be signed in to change notification settings - Fork 199
Support for ansible-core >= 2.12.0 #874
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
Comments
Ansible 5.x, which is not out yet, will require ansible-core 2.12. Ansible 4.x will continue to require ansible-core 2.11. So this won't be a high priority for me for at least a month or 2. However, patches with tests are welcome. |
FWIW, Ansible 5.0.1 is now out. |
we are updating our complete ansible infrastructure at the moment from 2.9 to the current ansible community version (5.0 = core 2.12) |
first test using https://github.com/Rosa-Luxemburgstiftung-Berlin/mitogen/tree/pr-ansible2.12 work well ... seems that mitogen is well prepared for ansible 2.12 |
Changing the supported version works for me, too. However, I didn't receive the intended error message before the change (as in the first post here), but rather the following:
That could be fixed by adding |
Bumped max supported version with Everything seems to be working in a medium size project (builtin, podman, grafana collections) |
Setting max version to 2.12 (I have 2.12.1) yeilded an error: |
I'm very glad that the support for 2.11 just got mainlined, but 2.12 is already out:
The text was updated successfully, but these errors were encountered: