# \[Default date 2025-12-03\] Collection inclusion: include cisco.ise in the Ansible community package **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg\ **Created:** [November 26, 2025, 8:37am UTC](https://forum.ansible.com/t/default-date-2025-12-03-collection-inclusion-include-cisco-ise-in-the-ansible-community-package/44898 "2025-11-26T08:37:06Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [April 8, 2026, 6:27pm UTC](https://forum.ansible.com/t/default-date-2025-12-03-collection-inclusion-include-cisco-ise-in-the-ansible-community-package/44898/8 "2026-04-08T18:27:32Z")
We’ve [removed the collection from Ansible 12](https://github.com/ansible-community/ansible-build-data/pull/559) because it [looked unmaintained](https://forum.ansible.com/t/43367). 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?](https://forum.ansible.com/t/45609) 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](https://github.com/CiscoISE/ansible-ise/actions/runs/21161776686). 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. --- _[View the full topic](https://forum.ansible.com/t/default-date-2025-12-03-collection-inclusion-include-cisco-ise-in-the-ansible-community-package/44898)._