Bullhorn #51

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #51, 2022-03-24 (Past Issues)

Welcome to The Bullhorn, our newsletter for the Ansible developer 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!


cybette shared


cybette said

The next Ansible Contributor Summit is happening soon! Mark your calendars for April 12, 2022 (Tuesday) and check out the event page - add your names and propose/vote on topics.

abuzachis contributed

The Amazon Web Services Working group is holding a monthly community meeting in #ansible-aws IRC channel at 17:30 UTC every fourth Thursday of the month. The first community meeting is scheduled on March 24th at 17:30 UTC. If you have something to discuss (e.g. a PR that needs help), add your request to the meeting agenda and join the IRC #ansible-aws channel / #aws:ansible.com room on Matrix.

cybette shared

The upcoming release of ansible-core 2.13 in May 2022 will coincide with the end-of-life of ansible 2.9 and ansible-base 2.10. See the detailed announcement here.


Antsibull ↗ 🐂

Tooling for building the Ansible package and collection documentation.

felixfontein contributed

antsibull-changelog 0.14.0 has been released (changelog). It speeds up the release process with ansible-core 2.13.


akasurde contributed

servicenow.itsm 1.3.0 is released. You can find more information about this new release in the changelog.


briantist said

The community.hashi_vault collection is still looking for feedback on implementing dedicated kv plugins and modules, come join the discussion and help shape new HashiCorp Vault content.

andersson007_ shared

As the number of collections contained in the ansible package continues to grow, we'd love to hear your opinions on the Future of ansible package community topic. Among other things, we discuss the following questions:

  • What do you see the purpose of the ansible package is?
  • Should we keep the process as-is, in other words, continue to include new collections?
  • Should we stop including new collections as they can be easily installed from Ansible Galaxy anyway?
  • Should we tighten the rules for new collections to get in, for example, requiring them to be "generic"?

Please share your thoughts with the Community!

samccann said

Ansible docs is proposing to archive older (EOL) releases (aka move them to a new archive site) - If you use an ansible release < 2.8, consider adding comments and voting on this topic at https://github.com/ansible-community/community-topics/issues/78

hunleyd contributed

If you use the community.postgresql collection, we'd love to hear your thoughts on this proposed change: https://github.com/ansible-collections/community.postgresql/issues/212


cybette shared

Join Ansible Pune group in "AWX Automation" - a collaborative effort with Dell Technologies on Wednesday, March 30 at 15:00 IST / 09:30 UTC. Check the details of this online meetup and RSVP here.


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!