Announcing a Change in Support for 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:
- 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.
- 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 in the cisco.asa repository so we can start the handover process.