Please add support for ansible.utils v3 #133
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 . |
|
It looks like 6.8.2 both dropped support for ansible.utils v2 and changed a parameter type. Both of these are breaking changes that should be reserved for a major release, but they're listed as bugfixes in the changelog. |
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)
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)
cisco.dnac and cisco.meraki due to compatibility issues
ansible-community/ansible-build-data#339
|
The parameter type change is possibly OK, assuming that it was not possible to use the parameter before (if the API rejected the value since it had the wrong type). Only if it was possible to successfully run the module when specifying a non-trivial value for that parameter before, then it is a breaking change. |
* 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
|
@felixfontein are you agree if 6.9.0 is released with ansible.utils: ">=2.0.0,<4.0", with that we don't drop support for v2 a add support for v3? |
Yes, that would be great! |
|
Ready @felixfontein @gotmax23 |
Added the compatibility to update specific credential/info of list of…
Prerequisites
Describe the bug
cisco.dnacv6.8.1 currently pins theansible.utilscollection to v2.dnacenter-ansible/galaxy.yml
Line 24 in a2cc158
Ansible 10, the next major version of the Ansible package will contain
ansible.utilsv3, socisco.dnacwill need to add support foransible.utilsv3 to remain included in the package. Ideally, the current major version ofcisco.dnaccould add support foransible.utilsv3 in addition toansible.utilsv2. If not, a new major version of this collection would need to be released that adds support foransible.utilsv3 and drops support for v2.Expected behavior
N/A
Screenshots
N/A
Environment (please complete the following information):
Additional context
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 efforts and for being part of the Ansible package!
The text was updated successfully, but these errors were encountered: