The Bullhorn #139

This week in Ansible Community
Issue #139, 2024-05-27 (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!

KEY DATES :stopwatch:


Ansible-Core :arrow_upper_right:

The ansible-core package contains the base engine and a small subset of modules and plugins. To see what’s planned for the next release, look at the ansible-core roadmaps.

ansible-announce shared

New Release: ansible-core v2.14.17 - New Release: ansible-core v2.14.17

ansible-announce shared

New Release: ansible-core v2.16.7 - New Release: ansible-core v2.16.7

ansible-announce contributed

New Release: ansible-core v2.17.0 - New Release: ansible-core v2.17.0

ansible-announce contributed

New Release: ansible-core v2.15.12 - New Release: ansible-core v2.15.12

Ansible :arrow_upper_right:

The Ansible package includes ansible-core and is a batteries-included package that provides a curated set of Ansible collections. See the Ansible roadmaps for future release plans.

mariolenz said

Ansible 9.6.0 package is here! :heart:
:link:Release announcement: Ansible community package 9.6.0
:minidisc:You can install it by running the following command:
python3 -m pip install ansible==9.6.0 --user
:arrow_right: Check Release Notes​:package::spiral_notepad: and Ansible 9 Porting Guide for more details!

mariolenz contributed

Ansible 10.0.0b1 package (pre-release) is here! :heart:
:link:Release announcement: Ansible community package 10.0.0b1 (Pre-Release)
:minidisc:You can install it by running the following command:
python3 -m pip install ansible==10.0.0b1 --user
:arrow_right: Check Release Notes​:package::spiral_notepad: and Ansible 10 Porting Guide for more details!

PROJECT UPDATES :hammer_and_wrench:

anwesha shared

Ansible Community Execution Environment Minimal 2.17-1 (Latest) is here :tada::tada::tada:. The container image includes fedora 40 and ansible-core 2.17.

Installation guide

  • podman pull
  • podman pull
  • podman pull

Antsibull :arrow_upper_right:

Tooling for building the Ansible package and collection documentation.

Felix Fontein contributed

antsibull-changelog 0.28.0 (antsibull-changelog/ at main · ansible-community/antsibull-changelog · GitHub) is out with a new option changelog_nice_yaml that allows to make changelogs/changelog.yaml pass ansible-lint’s YAML validation.

Felix Fontein shared

antsibull-changelog 0.27.0 (antsibull-changelog/ at main · ansible-community/antsibull-changelog · GitHub) is out with a new feature that allows to automatically add periods to the end of new module/plugin descriptions that do not end in punctuation. This makes these automatically generated entries comply with the Ansible changelog format (The Ansible Development Cycle — Ansible Community Documentation). It is enabled by default in new changelog configs, and can be explicitly enabled with setting add_plugin_period to true in existing configs.


Martin Jackson contributed

servicenow.itsm 2.6.0 has now been released, and is available on Galaxy and Automation Hub! It features new service catalog module support, as well as two key bugfixes which fix an inventory crash and improve performance when a query returns duplicate rows

Helen Bailey contributed 8.0.0 has been released with new features, bug fixes, and deprecated features. (see changelog for details).

Felix Fontein contributed

community.crypto 2.20.0 (community.crypto/ at main · ansible-collections/community.crypto · GitHub) has been released with bugfixes, a feature, three new modules for ACME handling, and some deprecations for internal code / docs fragments.

demetri shared

The ibm_zos_core 1.9.1 collection is now available on Galaxy and Automation Hub. This release includes 2 bugfixes and updated documentation. Review the blog or release notes for details.

Felix Fontein said

community.dns 3.0.0 (community.dns/ at main · ansible-collections/community.dns · GitHub) has been released. The most important change is that the collection now depends on community.library_inventory_filtering_v1 and repurposed the filter argument of the inventory plugins to use the filter mechanism from that collection. The 3.0.0 release also drops compatibility for End of Life Ansible/ansible-base/ansible-core releases; it now requires at least ansible-core 2.14.0. Another notable change is that the lookup plugins now append search domains to the provided domain name if that one cannot be found, using the search list configured in the system’s resolver configuration. This behavior can be changed with the new search option, now set by default to true. The old implicit default was false.

Felix Fontein shared

community.docker 3.10.0 (community.docker/ at main · ansible-collections/community.docker · GitHub) has been released with several new features. Note that this release deprecates the community.docker.docker_compose module. Please migrate to the community.docker.docker_compose_v2 module!

Felix Fontein said

community.general 9.0.0 (community.general/ at stable-9 · ansible-collections/community.general · GitHub) has been released with new features, bugfixes, deprecations, new modules and plugins, and some breaking changes. Please check out the changelog for more details!

community.general versions 8.6.1 (community.general/ at stable-8 · ansible-collections/community.general · GitHub) and 7.5.8 (community.general/ at stable-7 · ansible-collections/community.general · GitHub) have been released. The 8.x.y release train will only receive bugfixes from now on, and the 7.x.y release train will restrict to major bugfixes and security fixes.

community.general version 6.6.9 (community.general/ at stable-6 · ansible-collections/community.general · GitHub) was released which is the last 6.x.y release. The 6.x.y release train is therefore now End of Life. Thanks to everyone who contributed to the 6.x.y releases!


Call for Volunteers :postal_horn::postal_horn::postal_horn:

anwesha said

Hello Community,
Ansible has historically been released by Red Hat employees. Now, we are excited to open up the release process to the Community, recognizing the invaluable role you play in our ecosystem. The whole process is divided into two stages.
A. Automated release process
B. Release Managers from the Community
We have worked on the Release automation of the Ansible release process (read about it here). The second stage is to involve release managers from the Community. We have created a release managers’ working group, a platform for personal growth and learning. This working group, which has successfully handled the last few Ansible Releases, is a testament to the opportunities it provides for expanding your skills and contributing to a significant project like Ansible. We are eagerly looking for more volunteers to join the working group. If builds and releases excite you, this working group is an excellent place to start.

How to join?

To join, simply visit the Ansible Release Management matrix room here and join the conversation. You will find a welcoming community of like-minded individuals ready to guide you through the process.
On behalf of the Ansible Community, Happy Automating.


andersson007_ contributed

Please everyone share your feelings on the options for the Ansible community package future in the forum poll .

andersson007_ contributed

Feedback wanted on the How to improve cross-project contributor experience topic: can we enable contributors to easily be able to land and expand in our ecosystem?


samccann said

A couple of upcoming events, check out the details and RSVP:


Have any questions you’d like to ask, or issues you’d like to see covered? Please ask in! See you next time!