-
Notifications
You must be signed in to change notification settings - Fork 12
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 #112
Comments
This is somewhat urgent since many network collections already explicitly require ansible.netcommon >= 6.0.0, which requires ansible.utils >= 3.0.0. |
Ping @bvargasre @wastorga @DbarrantesE since you recently committed to this repo. |
@wastorga, @racampos, @jbogarin, you are listed in the Ansible package metadata as maintainers of this collection. Can you please take a look at this? Thanks! |
@felixfontein @gotmax23 cisco.ise add support to ansible.utils v3 in last version (2.7.0). If all is ok, please feel free to close issue. |
cisco.ise, the last collection to depend on `ansible.utils<3.0.0`, has been updated. Ref: CiscoISE/ansible-ise#112 (comment)
Thanks! |
cisco.ise, the last collection to depend on `ansible.utils<3.0.0`, has been updated. Ref: CiscoISE/ansible-ise#112 (comment)
Prerequisites
Describe the bug
cisco.ise
currently pins theansible.utils
collection to v2.ansible-ise/galaxy.yml
Line 20 in e830197
Ansible 10, the next major version of the Ansible package will contain
ansible.utils
v3, socisco.ise
will need to add support foransible.utils
v3 to remain included in the package. Ideally, the current major version ofcisco.ise
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.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 work and for being part of the Ansible package!
The text was updated successfully, but these errors were encountered: