Bullhorn #43

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #43, 2022-01-28 (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, please reach out to us at the-bullhorn@redhat.com, or chat with us in the Ansible Social room on Matrix.


cybette contributed


andersson007_ contributed

Dear collection maintainers,

This is important for your collections!

  • In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that has just been closed.
  • To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page.
  • If you do not want to get notifications about related discussions, please subscribe only to Issues.
  • Please read the brief guidelines on how the repository should be used.
  • Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!

Thank you!


andersson007_ shared

community.postgresql 1.6.1 has been released. Among other improvements, the postgresql_info module now works with AWS RDS PostgreSQL instances, thanks to marcosdiez!

andersson007_ said

community.mysql 3.1.0, 2.3.3, and 1.4.4 have been released.

markuman shared

community.aws 3.0.1 has just been released.

mariolenz shared

community.vmware 2.0.0 has been released. Note that this is a new major version, meaning backwards incompatible changes like breaking changes and removed features.


felixfontein contributed

The proposal on semantic markup in plugin/module DOCUMENTATION has been updated to allow to more easily reference plugins in the seealso: section. See this message for details.

felixfontein shared

The vote on whether to use FQCN for ansible.builtin modules (https://github.com/ansible-community/community-topics/issues/58) is completed. The proposal has been accepted with a broad majority both in the steering committee and in the community.

felixfontein shared

There is a new active vote on simplifying the collection inclusion procedure for adding new collections to the Ansible community package: https://github.com/ansible-community/community-topics/issues/63 The vote is active until 2022-02-02.

felixfontein contributed

The voting on the proposed roadmap for Ansible 6 has concluded on 2022-01-26. You can see the discussions and result in this issue.

samccann contributed

We're looking for feedback on how to write better changelogs so our porting guides give better information to users. Please comment at https://github.com/ansible-community/community-topics/issues/64 with your ideas.

gundalow shared

Changelogs are an important way to let users know about new features, and more importantly potentially backwards incompatible changes which might require you to update how you use a certain Collection. Based on feedback, we've realised that these aren't always written consistently. We are looking for your feedback (especially from end users and maintainers) on how we can give a better experience. We'd love your thoughts via community-topics#64.

samccann contributed

We're working on better community and contributor guidlines for Ansible. Please comment at https://github.com/ansible-community/community-topics/issues/60 with your ideas!


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.

gundalow said

ansible-galaxy is currently being updated to allow collection verification using gpg, this will be released in ansible-core 2.13. This will allow verifying the authenticity of MANIFEST.json before installing and manually at any time.

The Galaxy server will be queried for signatures and a list of supplemental URLs can be provided in the requirements file: ``` collections: - name: ns.coll signatures: - https://.../test.asc - file:///.../test.asc

``` You can check out the progress and let us know if the proposal works for your use case. We'd love your feedback via ansible#76681.


csmart said

In case it's useful, a blog post on how I'm currently setting up my Ansible dev environment https://blog.christophersmart.com/2021/12/27/setting-up-an-ansible-dev-environment/


cybette said

DevConf.cz 2022 is happening right now (Jan 28-29), and you can find a list of Ansible related talks here. Sessions of note include Ansible Community Meetup Jan 28 @ 16:00 UTC, and What’s New & Ahead in the Ansible Community Jan 29 @ 15:30 UTC.

cybette shared

There's an "Ansible Anwendertreffen" (Ansible user meeting) which will be held on Feb 15, 2022. This is a virtual event conducted in German. If you are interested, you can find the details and registration info here. The CFP is still available until Jan 31, so act fast if you'd like to present at this event!


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!