# Deprecation Announcement for the cisco.asa Ansible Collection

**URL:** <https://forum.ansible.com/t/deprecation-announcement-for-the-cisco-asa-ansible-collection/38939>\
**Category:** Get Help\
**Tags:** network\
**Created:** [December 6, 2024, 5:16am UTC](https://forum.ansible.com/t/deprecation-announcement-for-the-cisco-asa-ansible-collection/38939 "2024-12-06T05:16:34Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![mistertom](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mistertom/32/7514_2.png) [@mistertom](https://forum.ansible.com/u/mistertom)\
**Post date:** [February 7, 2025, 6:17pm UTC](https://forum.ansible.com/t/deprecation-announcement-for-the-cisco-asa-ansible-collection/38939/8 "2025-02-07T18:17:40Z")

</div>

> [@Remove cisco.asa from community package](https://forum.ansible.com/t/remove-cisco-asa-from-community-package/38960/7):
>
> Indeed, It can still be installed from Ansible Galaxy, as @russoz pointed out. The main issue that prompted removal is No guarantees of compatibility with ansible-core versions \>2.17 will be provided Ansible 11 ships with Core 2.18 and 12 will ship with 2.19, and one of the most basic requirements is that collections in the package test against the version of ansible-core that we include in a given version of Ansible.

My current deployment is RHEL/CentOS compatible 9.x which has ansible-core 2.14.x. Being \<= 2.17.x I think the deprecation plans may not impact my deployment. This software development moves so fast. I initially was concerned I needed immediate plans to move away from dependencies on the collection, but it looks like I may have some years before RHEL/CentOS are shipping with ansible-core greater than 2.17.

---

_[View the full topic](https://forum.ansible.com/t/deprecation-announcement-for-the-cisco-asa-ansible-collection/38939)._