The Bullhorn #228

This week in Ansible Community
Issue #228, 2026-05-18 (Past Issues)

Welcome to The Bullhorn, our newsletter for the Ansible Community. If you have any questions or content you’d like to share, you’re welcome to chat with us in the Ansible Social room on Matrix, and mention newsbot to have your news item tagged for review for the next weekly issue!

General news updates :speaker_low_volume:

Security by default and the Cyber Resilience Act

anwesha said

Security as Default, Not an Afterthought: The CRA’s Real Message

The European Union’s Cyber Resilience Act (CRA) is ushering in a new era for the software supply chain, moving from voluntary “best effort” security to mandatory standards. In a recent forum post, the community team outlines what this means for the Ansible ecosystem.
The core takeaway is a shift toward “Security by Default.” Rather than imposing a burden on individual contributors, Red Hat is stepping up as the Open Source Software Steward for Ansible. This means Red Hat will handle the administrative and legal heavy lifting—such as vulnerability reporting to ENISA and maintaining SBOMs (Software Bill of Materials)—so that the community can focus on innovation.

What to expect?

For Maintainers: Improved security hygiene, including the recent requirement for signed commits and enhanced SECURITY.md documentation.
For Users: Greater transparency and confidence in the security posture of the collections and tools you rely on.
Timeline: Reporting of actively exploited vulnerabilities begins September 11, 2026, with full compliance required by late 2027.

Ansible isn’t just complying with the CRA; we are using it as a catalyst to build a more robust, “security-first” automation platform.
Read the full discussion and share your thoughts on the Forum.

Unified collection testing strategy

dbrennand shared

Unified Collection Testing Strategy
We’ve kicked off an initiative to unify Ansible collection testing! To build a strategy that works for everyone, we need to hear as many voices from the community as possible.

Your participation is key to ensuring we consider a broad set of views and real world use cases. Please join us in shaping this strategy, keep an eye on the evolving discussion, and have your say here: Unified Collection Testing Strategy - Kick off & Landscape Overview.

Collection updates :magic_wand:

community.dns 4.0.0 release

Felix Fontein shared

community.dns 4.0.0 (community.dns/CHANGELOG.md at main · ansible-collections/community.dns · GitHub) has been released. It drops support for ansible-core < 2.18 (and thus Python < 3.8), and for dnspython < 2.0.0.

ansible.mysql 5.0.1 release

andersson007_ contributed

The ansible.mysql collection version 5.0.1 has been released!

infra.aap_utilities 3.2.0 release

Sean Sullivan said

infra.aap_utilities 3.2.0 has been released.
This Ansible collection provides utility roles for usage with Ansible Automation Platform.
Visit GitHub - redhat-cop/aap_utilities: Ansible Collection for automated deployment of AAP and other objects for general use · GitHub For more information and updates.

amazon.aws 11.3.0 release

abuzachis contributed

amazon.aws 11.3.0 has been released including new features and improvements to the autoscaling_group, elb_application_lb, elb_application_lb_info, elb_classic_lb, event_source_aws_cloudtrail, kms_key, s3_bucket, s3_object_info modules.

For full details, check out the changelog.

ansible.posix 2.2.0 release

hsaito shared

ansible.posix 2.2.0 has been released. It covers the latest ansible-core (devel).

Certified collections weekly update

Thirteen certified collections updated

dbrennand shared

Certified collections updated this week:

Community events and meetups

Upcoming meetups and working groups

Three upcoming community events

dbrennand shared

Other events and releases

Use the Ansible Forum to see other events and releases.

Join the Ansible community

Looking for ways to get involved? See how can I help for some ideas!

You can find easy issues in collections and other projects for code or documentation contributions.

That’s all for now!

Have any questions you’d like to ask, or issues you’d like to see covered? Please ask in #social:ansible.com! See you next time!

2 Likes