# Announcing a Change in Support for cisco.asa: Transitioning to Community Maintenance **URL:** \ **Category:** Get Help\ **Tags:** cisco, network\ **Created:** [September 13, 2025, 7:07pm UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482 "2025-09-13T19:07:05Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![AAYUSH\_ANAND](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/aayush_anand/32/8150_2.png) [@AAYUSH\_ANAND](https://forum.ansible.com/u/AAYUSH_ANAND)\ **Post date:** [September 13, 2025, 7:07pm UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/1 "2025-09-13T19:07:05Z")
**Announcing a Change in Support for [cisco.asa](https://github.com/ansible-collections/cisco.asa): Transitioning to Community Maintenance** The cisco.asa Ansible collection is entering a new phase. As of now, this collection will transition from being officially supported by Red Hat to a community-maintained model. **Why the Change?** After careful consideration, we’ve decided to make this change for two main reasons: 1. **Vendor Technology Lifecycle** : Cisco Systems has moved on from its ASA firewall technology in favor of its next-generation Firepower solutions. This shift makes it less of a priority for us to continue supporting ASA. 2. **Low Community and Customer Adoption** : Over the past year, we’ve seen minimal activity related to this collection, with no customer support escalations and very few issues opened in the GitHub repository. This lack of engagement means it’s time for the community to step in and take ownership. **What This Means for the Community** - **The Collection Lives On** : Don’t worry, the cisco.asa collection will remain available on GitHub. We’re not deleting it! - **Change in Maintenance** : Red Hat will no longer provide updates, bug fixes, or support. The future development and health of the collection will depend on the efforts of community maintainers. - **Future on Automation Hub** : The collection will eventually be removed from Red Hat Automation Hub once the transition to the community is complete. However, it will remain available in Ansible Galaxy. **A Call to Action: Become a Community Maintainer!** If your organization still relies on Cisco ASA and you want to ensure this collection continues to thrive, we strongly encourage you to step up and become a community maintainer.f you’re interested, please reply to this thread or comment on the pinned GitHub [issue](https://github.com/ansible-collections/cisco.asa/issues/274) in the cisco.asa repository so we can start the handover process. ---
**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:** [January 15, 2026, 7:10pm UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/2 "2026-01-15T19:10:14Z")
> [@AAYUSH\_ANAND](#): > > **A Call to Action: Become a Community Maintainer!** > > If your organization still relies on Cisco ASA and you want to ensure this collection continues to thrive, we strongly encourage you to step up and become a community maintainer.f you’re interested, please reply to this thread or comment on the pinned GitHub [issue](https://github.com/ansible-collections/cisco.asa/issues/274) in the cisco.asa repository so we can start the handover process. I am a user of the `cisco.asa` collection and would like to know how to become involved for community maintenance. ---
**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 2, 2026, 7:19pm UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/3 "2026-02-02T19:19:10Z")
To follow up with my desire to keep some form of the `cisco.asa` collection working with Ansible, here is what I have been doing: - Successfully Testing [`cisco.asa` collection version 6.1.0](https://galaxy.ansible.com/ui/repo/published/cisco/asa/) with recent/supported versions of Ansible and dependencies - Python version 3.12.x (Control Node OS RHEL 9.x compatible with python 3.12.x venv) - `ansible-core` version 2.20.x - `ansible` community version 13.3.x - Cisco [ASA version 9.23.x](https://www.cisco.com/c/en/us/td/docs/security/asa/asa923/release/notes/asarn923.html) - My testing is mostly limited to the `asa_command`, `asa_config`, and `asa_facts` modules based on my current simple use cases. I am also testing `net_put` from the netcommon collection (for scp uploads like firmware updates). If there is no further [guidance from the team managing the existing `cisco.asa` collection code-base to transition that to community maintenance](https://github.com/ansible-collections/cisco.asa/issues/274), I am thinking about trying the following: - Do further testing with an independent fork of the `cisco.asa` collection to see if I am able to make any meaningful contributions under an independent code-base with the goal of compatibility with future `ansible-core` releases. Things like resolving Deprecation Warnings from ansible-core 2.20. - The current release `cisco.asa` collection version 6.1.0 appears to be stable with ansible-core 2.20, so there is likely not much work needed other than keeping pace with underlying ansible-core deprecations or future api changes. ---
**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 10, 2026, 1:53am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/4 "2026-02-10T01:53:28Z")
I’m trying to learn more about the `cisco.asa` collection codebase and github setup, it looks like the CI sanity tests are succeeding for all currently supported python and ansible-core versions but [failing for sanity-py3.12-devel, sanity-py3.12-milestone, sanity-py3.13-devel, and sanity-py3.13-milestone](https://github.com/ansible-collections/cisco.asa/actions/runs/21846821563). I am new to GitHub Actions CI and new to ansible sanity testing. Any clue **what these failures mean, or what I could do as a community contributor to help resolve them?** ![cisco-asa_sanity-test_devel-milestone_2026-02-09_202645](https://us1.discourse-cdn.com/ansible/original/2X/d/d6442e76082da3ada7144cace849d2acc8813df1.png) ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 10, 2026, 5:15am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/5 "2026-02-10T05:15:38Z")
If you copy `tests/sanity/ignore-2.20.txt` over to `tests/sanity/ignore-2.21.txt` this should go away. (Also I wouldn’t run sanity tests for specific Python versions in CI, but simply run `ansible-test sanity --docker` for every ansible-core version.) ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [February 10, 2026, 10:27am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/6 "2026-02-10T10:27:53Z")
@mistertom It’s great to hear that you are considering being involved in this collection for community maintenance bits 🙂 @felixfontein in his response above kindly provided the fix for the sanity tests. If there is anything I can do to help assist you with this then please let me know! @felixfontein maybe in the future this collection could be a good candidate for using `antsibull-nox` RE: > (Also I wouldn’t run sanity tests for specific Python versions in CI, but simply run `ansible-test sanity --docker` for every ansible-core version.) ---
**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 10, 2026, 4:06pm UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/7 "2026-02-10T16:06:44Z")
I will try to submit a PR for this CI issue (copy `tests/sanity/ignore-2.20.txt` over to `tests/sanity/ignore-2.21.txt`). It will by my first PR attempt for an ansible community contribution, is there any quick-start doc or guide that I should follow for making the PR? I’m guessing I clone a fork of the project repo and then make the applicable change and use that to submit the PR against the original project repo when ready. If I run `ansible-test sanity --docker` locally, how can I cause that to run against a specific core version and/or dev/milestone? When I ran that recently it appeared to use different versions of python, but maybe not any specific version of ansible-core? It is not clear to me from [Sanity Tests — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/dev_guide/testing_sanity.html). Do I need to install dev/milestone core source-code then `source hacking/env-setup`, or should the core version selection be handled for me automatically by the `--docker` option? ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [February 10, 2026, 4:33pm UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/8 "2026-02-10T16:33:09Z")
Hi @mistertom - Great stuff! > is there any quick-start doc or guide that I should follow for making the PR? I’m guessing I clone a fork of the project repo and then make the applicable change and use that to submit the PR against the original project repo when ready. Yes, you can use [Creating your first collection pull request](https://docs.ansible.com/projects/ansible/latest/community/create_pr_quick_start.html) as reference for your PR, but seems like you got the flow already 🙂 ---
**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 11, 2026, 2:46am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/9 "2026-02-11T02:46:34Z")
I have a PR here [tests/sanity/ignore-2.21.txt: fix sanity tests for dev/milestone by notesbytom · Pull Request #276 · ansible-collections/cisco.asa](https://github.com/ansible-collections/cisco.asa/pull/276) Let me know if this looks ready for review or is missing something. I tried to follow the document [Creating your first collection pull request](https://docs.ansible.com/projects/ansible/latest/community/create_pr_quick_start.html) which you referred me to. I appreciate the help getting me started with contributing a little as a community member. ---
**Author:** ![jorgenspange](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jorgenspange/32/9667_2.png) [@jorgenspange](https://forum.ansible.com/u/jorgenspange)\ **Post date:** [September 3, 2026, 7:56am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/10 "2026-09-03T07:56:27Z")
Good day! @KB-perByte would it be an idea that I become a maintainer here? Currently it seems like most of the maintainers are RHEL employees, and as RHEL does not support this collection anymore, maybe someone from the community could do it, to drive things forwards? Br ---
**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\ **Post date:** [September 3, 2026, 8:22am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/11 "2026-09-03T08:22:38Z")
@jorgenspange, you are equally a part of our community, and you have been a consistent contributor. I’ll get things set up for you. Thanks a lot for reaching out. Regards. -KB-perByte ---
**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\ **Post date:** [September 3, 2026, 10:02am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/12 "2026-09-03T10:02:09Z")
[Adding community maintainers to cisco.asa · Issue #281 · ansible-collections/cisco.asa · GitHub](https://github.com/ansible-collections/cisco.asa/issues/281) Added a small issue here to draft all the activity and I’ll add you the access shortly. @jorgenspange ---
**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\ **Post date:** [September 3, 2026, 10:04am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/13 "2026-09-03T10:04:42Z")
@mistertom I see you have been active here [Announcing a Change in Support for cisco.asa: Transitioning to Community Maintenance · Issue #274 · ansible-collections/cisco.asa · GitHub](https://github.com/ansible-collections/cisco.asa/issues/274) Are you too interested in taking up interest in being a maintainer? Please let us know. Regards ---
**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:** [September 3, 2026, 3:11pm UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/14 "2026-09-03T15:11:24Z")
Yes, I haven’t had time to dedicate to the collection, but I do hope to continue to contribute to maintaining this as I still use it. I think you gave me some access to be a maintainer already. If there is anything you wanted me to do for @jorgenspange let me know. ---
**Author:** ![jorgenspange](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jorgenspange/32/9667_2.png) [@jorgenspange](https://forum.ansible.com/u/jorgenspange)\ **Post date:** [September 4, 2026, 9:07am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/15 "2026-09-04T09:07:16Z")
@mistertom Yeah, there’s some PRs id like merged: PR #251: [https://github.com/ansible-collections/cisco.asa/pull/251](https://urldefense.com/v3/ __https://github.com/ansible-collections/cisco.asa/pull/251__ ;!!L0Ua0Wts!bJhjNM-EfahoTsiuwDqDUTMQtE0pctcQkFzyVTiWIJzba8iMDrlnGwjfQjqse19iDeFD0IcHjsWCsu8pBo6OCk91fsz0$ "https://urldefense.com/v3/\_\_https://github.com/ansible-collections/cisco.asa/pull/251\_\_;!!L0Ua0Wts!bJhjNM-EfahoTsiuwDqDUTMQtE0pctcQkFzyVTiWIJzba8iMDrlnGwjfQjqse19iDeFD0IcHjsWCsu8pBo6OCk91fsz0$") PR #255: [https://github.com/ansible-collections/cisco.asa/pull/255](https://urldefense.com/v3/ __https://github.com/ansible-collections/cisco.asa/pull/255__ ;!!L0Ua0Wts!bJhjNM-EfahoTsiuwDqDUTMQtE0pctcQkFzyVTiWIJzba8iMDrlnGwjfQjqse19iDeFD0IcHjsWCsu8pBo6OCnTggO6R$ "https://urldefense.com/v3/\_\_https://github.com/ansible-collections/cisco.asa/pull/255\_\_;!!L0Ua0Wts!bJhjNM-EfahoTsiuwDqDUTMQtE0pctcQkFzyVTiWIJzba8iMDrlnGwjfQjqse19iDeFD0IcHjsWCsu8pBo6OCnTggO6R$") PR #280: [https://github.com/ansible-collections/cisco.asa/pull/280](https://urldefense.com/v3/ __https://github.com/ansible-collections/cisco.asa/pull/280__ ;!!L0Ua0Wts!bJhjNM-EfahoTsiuwDqDUTMQtE0pctcQkFzyVTiWIJzba8iMDrlnGwjfQjqse19iDeFD0IcHjsWCsu8pBo6OCt6Z9RyR$ "https://urldefense.com/v3/\_\_https://github.com/ansible-collections/cisco.asa/pull/280\_\_;!!L0Ua0Wts!bJhjNM-EfahoTsiuwDqDUTMQtE0pctcQkFzyVTiWIJzba8iMDrlnGwjfQjqse19iDeFD0IcHjsWCsu8pBo6OCt6Z9RyR$") If you could help with that and also release a new version that would be very nice! ---
**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\ **Post date:** [September 5, 2026, 9:27am UTC](https://forum.ansible.com/t/announcing-a-change-in-support-for-cisco-asa-transitioning-to-community-maintenance/44482/16 "2026-09-05T09:27:43Z")
@jorgenspange I have added access to you, can you check your invites and accept. Thanks for your patience. Please let us know over Ansible forum if you need any help moving forward.