The Bullhorn #132

This week in Ansible Community

Issue #132, 2024-03-15 (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:

cybette shared


Antsibull :arrow_upper_right:

Tooling for building the Ansible package and collection documentation.

Felix Fontein contributed

antsibull-docs 2.8.0 has been released with new bugfixes and features. The included Sphinx extension now supports selecting a color scheme, including a none scheme that makes it easy to set your own color using CSS custom properties.

PROJECT UPDATES :hammer_and_wrench:

AWX Project :arrow_upper_right:

AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. Join the AWX discussion in the Ansible Community Forum.

chadams contributed

o/ Hey everyone! I just wanted to note a couple big features that have landed in devel in the last week or two that are of note and will end up in the next release.

  • AWX now supports Postgres 15 and it is the default version that will be used - PR Link
  • After a long wait, I am happy to announce that the AWX Operator now has readiness and liveliness probes, and the migrations run in a k8s job - PR Link

Please see the announcement on the forum for more details!


Simon Dodsley contributed

purestorage.flasharray 1.27.0 (changelog) has been released with minor additions and bugfixes. This release also changes the minimum FlashArray Purity version to 6.1.0.

Martin Jackson contributed

servicenow.itsm 2.4.0 has been released! Changelog here.

aleks_vagachev contributed

the community.clickhouse collection version 0.4.0 has been released!

gomathiselvi said

kubernetes.core 3.0.1 is released with bugfixes. (see Changelog for details)

kubernetes.core 2.4.2 is released with bugfixes. (see Changelog for details)


Oranod said

Have you ever noticed that the ecosystem page on the docsite does not feature many of the fantastic community projects that are available to help with Ansible automation? We have too. And the reason comes down to lack of clearly defined inclusion criteria for projects.

We’d invite you to help us agree on and define “table stakes” for projects to be included on the ecosystem page. An obvious criteria, for example, is that projects should have an OSI-approved license. But what else should we consider? If you have an opinion, let us hear your voice. Please join us in our forum discussion and tell us what you think.

mariolenz said

There is a vote on making it easier to remove officially unmaintained collections from Ansible, and to remove them faster. Please vote on what you think about this!


Oranod shared

Send us your “see also” suggestions for module docs.

The Ansible community team at Red Hat gathered lots of feedback at this year’s CfgMgmtCamp 2024. One of those things was to expand the use of the “See also” section in module documentation. This is an often under-used, but very useful, section that can group related modules that build and expand on each other’s functionality and help users find the right module to achieve their goals.

We thought it might be fun, and interesting, to put a call to action out and ask the community what modules could form a “See also” section. If you have ideas for modules that have similar functionality or are related in some way, please let us know. Visit us on the forum and add your suggestion to our “Call to action” thread. We can then try and work with the collection owners to update their documentation.

samccann shared

Looking to help out in Ansible but not sure where to start? Take a look at some easyfix or good first issues:


cybette said

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


Zhenech shared

Data from dynamic inventory plugins can contain Jinja expressions and lead to remote code execution, see this post for a detailed writeup.


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