The inclusion request: Collection review: cisco.ise · ansible-collections/ansible-inclusion · Discussion #46 · GitHub
It’s been reviewed and approved by two SC members.
The default inclusion date is 2025-12-03.
Some background: Collection review: cisco.ise · ansible-collections/ansible-inclusion · Discussion #46 · GitHub
The thread which eventually resulted in the removal of the collection from Ansible: [Vote ended on 2025/06/22] Possibly unmaintained collection: cisco.ise
1 Like
-1. I don’t think this collection should be added automatically without a full vote, given its history and that we just removed it within the past year six months. I would rather wait at least another Ansible release cycle and then evaluate whether it is still following the requirements and should be re-added.
I recall we also suggested that the Cisco network collections set up some kind of automated process to handle ansible.netcommon dependency updates so the community package release managers don’t need to manually intervene each time. Has that situation been addressed?
I’m also quite interested in hearing about this. I’m OK with re-adding the collection already now if this has been addressed in a satisfactory way.
(Especially considering that we had this problem twice already with this collection: Collection not compatible with ansible.utils 5.x.y · Issue #144 · CiscoISE/ansible-ise · GitHub GitHub · Where software is built)
Hi,
Regarding the automated process: it is not implemented yet. We are still handling the ansible.netcommon dependency updates manually. However, we have started working on automating this and we hope to have an initial version ready next week.
This automation should help not only for the cisco.ise collection but also for other collections we maintain (dnac, catalyst, meraki,), as it will significantly reduce the amount of manual work needed for future releases.
1 Like