[Default date 2025-12-03] Collection inclusion: include cisco.ise in the Ansible community package

Project Discussions
1

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.

2

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
3

-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.

4

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?

5

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)

6

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
7

Hey folks, any updates on this topic?

1 Like
8

We’ve removed the collection from Ansible 12 because it looked unmaintained.

ATM I prefer to not add any more collections from Cisco. It feels to me like they stop maintaining collections without letting us know or announcing this in a way that we can see it. See Cisco.dnac has been deprecated, what to do about his? for an example. (For the record: It’s a little bit unclear if cisco.ucs is maintained or not.)

BTW it looks like the last CI run has been Jan 20.

At the end of the day, their customers can always install the collection directly from galaxy. But the problems I’ve seen with Cisco collections in the past plus there hasn’t been any CI run for more than 2 months… I think we should be really careful adding Cisco collections to the ACP.

1 Like
9

Maybe I should start a new thread for this, though do we see this problem with other collections? More parts of Ansible Engineering are looking at dependabot, so it this is a common issue, we could look at submitting a patch to dependabot.