-
Notifications
You must be signed in to change notification settings - Fork 5
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
Please add support ansible.utils v3 #38
Please add support ansible.utils v3 #38
Comments
This is somewhat urgent since many network collections already explicitly require ansible.netcommon >= 6.0.0, which requires ansible.utils >= 3.0.0. |
Hi @felixfontein , @gotmax23 . |
2.16.17 dropped support for ansible.utils v2. This change is semver incompatible and should be reverted in the next v2 release and held for v3, hence the two different constraints. Relates: meraki/dashboard-api-ansible#38
We could constrain this to `<2.16.17`, but it's expected that the next minor/patch release of cisco.meraki v2 will revert these changes Relates: meraki/dashboard-api-ansible#38
We could constrain this to `<2.16.17`, but it's expected that the next minor/patch release of cisco.meraki v2 will revert these changes Relates: meraki/dashboard-api-ansible#38
* 10: pin cisco.dnac due to ansible.utils compat issues 6.8.2 dropped support for ansible.utils v2. This change is semver incompatible and should be reverted in the next v6 release and held for v7, hence the two different constraints. * 9: blocklist semver-incompatible cisco.dnac 6.8.2 We could constrain this to `<6.8.2`, but it's expected that the next minor/patch release of cisco.dnac v6 will revert these changes Relates: cisco-en-programmability/dnacenter-ansible#133 (comment) * 8: blocklist semver-incompatible cisco.dnac 6.8.2 We could constrain this to `<6.8.2`, but it's expected that the next minor/patch release of cisco.dnac v6 will revert these changes Relates: cisco-en-programmability/dnacenter-ansible#133 (comment) * 10: pin cisco.meraki due to ansible.utils compat issues 2.16.17 dropped support for ansible.utils v2. This change is semver incompatible and should be reverted in the next v2 release and held for v3, hence the two different constraints. Relates: meraki/dashboard-api-ansible#38 * 9: blocklist semver-incompatible cisco.meraki We could constrain this to `<2.16.17`, but it's expected that the next minor/patch release of cisco.meraki v2 will revert these changes Relates: meraki/dashboard-api-ansible#38 * 8: blocklist semver-incompatible cisco.meraki We could constrain this to `<2.16.17`, but it's expected that the next minor/patch release of cisco.meraki v2 will revert these changes Relates: meraki/dashboard-api-ansible#38
Ready @felixfontein @gotmax23 |
It looks good to me now. Thanks for the quick responses and for fixing the issue! Would it be possible to do the same for https://github.com/CiscoISE/ansible-ise/? |
cisco.meraki
v2.16.16 currently pins theansible.utils
collection to v2.dashboard-api-ansible/galaxy.yml
Line 21 in 6302dcf
Ansible 10, the next major version of the Ansible package will contain
ansible.utils
v3, socisco.meraki
will need to add support foransible.utils
v3 to remain included in the package. Ideally, the current major version ofcisco.meraki
could add support foransible.utils
v3 in addition toansible.utils
v2. If not, a new major version of this collection would need to be released that adds support foransible.utils
v3 and drops support for v2.Note that Ansible 10 will not be released until next spring, so you have a bit of time, but ideally, this could be addressed sooner rather than later. Thanks for your work and for being part of the Ansible package!
The text was updated successfully, but these errors were encountered: