This week in Ansible Community
Issue #133, 2024-03-25 (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
cybette shared
- 2024-03-25: ETA for Ansible-Core 2.14.15, 2.15.10, and 2.16.5
- 2024-03-26: ETA for Ansible 9.4.0 release
- 2024-03-26: DaWGs meeting, 16:00 UTC
- 2024-03-27: Community WG meeting, 19:00 UTC
- 2024-03-28: Bullhorn #134 content deadline, 18:00 UTC
MAJOR NEW RELEASES
Antsibull
Tooling for building the Ansible
package and collection documentation.
Felix Fontein shared
antsibull-core 3.0.0 has been released with some breaking changes and removed deprecated features, and a bugfix. It no longer depends on
sh
, and requirespydantic
v2.
Felix Fontein said
antsibull-changelog 0.26.0 has been released with improved MarkDown format that renders better with python-markdown and mkdocs, and galaxy_ng’s markdown renderer.
Felix Fontein contributed
antsibull-docs 2.9.0 and antsibull 0.61.0 have been released. These are maintenance releases supporting the new antsibull-core 3.0.0 release (resp. antsibull-core v3 in general). Besides that, antsibull has a bugfix, and antsibull-docs has no other change.
COLLECTION UPDATES
Sean Sullivan shared
infra.controller_configuration 2.7.1 has been released. This Ansible collection allows for easy interaction with an AWX or Ansible Controller server via Ansible roles using the AWX/Controller collection modules.
Visit the repo for more information and updates.
briantist contributed
community.hashi_vault
version6.2.0
has been released, with a whole new set of modules for working with Vault’s database secrets engine. See the full changelog.
mariolenz said
The vote on making it easier to remove officially unmaintained collections from the Ansible community package, and to remove them faster, has been accepted. You can find the new process here.
PROPOSALS - DISCUSS AND VOTE!
Felix Fontein said
I’ve started a discussion of deprecating the community.docker.docker_compose module, which allows to use Docker Compose v1. Note that Docker Compose v1 is End of Life since July 2022, and it gets harder to use it with modern Docker (it no longer works with Docker 26.0.0) and Docker SDK for Python (it no longer works with Docker SDK for Python 7.0.0). If you are aware of active users of the
docker_compose
module, or are yourself using it actively, please take a look at the issue and comment if you don’t plan to move to thecommunity.docker.docker_compose_v2*
modules, or can’t move to them for some reasons. Thanks!
HELP WANTED
Oranod contributed
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 said
Looking to help out in Ansible but not sure where to start? Take a look at some easyfix or good first issues:
- across multiple collections
- for all other Ansible projects
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!