Bullhorn #29

Ansible Bullhorn banner

The Bullhorn

A Newsletter for the Ansible Developer Community Issue #29, 2021-07-01 (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 comment on this GitHub issue.



The Ansible Community team announced the availability of Ansible 4.2.0 on June 30th. This update contains bugfixes and new, backwards compatible features in the contained collections. The release makes use of Ansible-core-2.11. There may be changes to the playbook language or other backwards incompatibilities. Please see the porting guide for details.

For what's new in this release and how to get it, please see Toshio Kuratomi’s email to the ansible-announce list.

We're planning to release Ansible 5.0.0 in November 2021, bringing in the Ansible-core-2.12 release.


The Ansible Core team announced the maintenance releases of Ansible-Core 2.11.2, Ansible-Base 2.10.11, and Ansible 2.9.23 on June 22nd. These releases fix a templating security issue, CVE-2021-3583, in addition to several other bugs. Follow this link for Rick Elrod’s email to the ansible-devel mailing list, to obtain details on what’s new, installation instructions, and schedule for future releases.


The changelog generator antsibull-changelog 0.11.0 has been released, with support for detecting new roles in collections.

ansible-pygments 0.1.0 has been released. This package provides a Pygments lexer ansible-output for highlighting ansible-playbook output, and the Pygments color scheme used for the Ansible docsite.


  • Foreman Ansible Collection - theforeman.foreman 2.1.0 and 2.1.1 were released. Most notable changes include:
  • more *_info modules: content_view_info, content_view_version_info, domain_info, host_errata_info, repository_set_info, setting_info, subnet_info, and subscription_info
  • new roles: content_rhel, hostgroups, content_views, organizations, and content_credentials
  • compute_resource module can now better manage Azure compute resources
  • important bugfix in 2.1.1: host, hostgroup - don’t override already set parameters when passing an activation key only (and vice versa).
  • Ansible Collection for ServiceNow ITSM - servicenow.itsm 1.1.0 released. Most Notable changes include:
  • support for refresh_token in the login mechanism
  • support for specifying queries in the *_info modules.
  • Openstack Ansible Collection - openstack.cloud 1.5.0 was released with a lot of bugfixes, improvements, and 3 new modules: address_scope, dns_zone_info, and floating_ip_info.
  • Podman Ansible Collection - containers.podman 1.6.0 and 1.6.1 were released. New module podman_play was introduced for playing Kubernetes YAML files as Podman Pods.
  • Ansible VMware vSphere Collection - vmware.vmware_rest 2.0.0 released (new major version). Notable changes:
  • a new set of modules to manage the vCenter appliances (VCSA)
  • modules to manage Library, including snapshoting and booting VM through an OVF.
  • TrendMicro DeepSecurity Ansible Collection - trendmicro.deepsec 1.1.0 released. Two new modules are introduced in this release:
  • deepsec_apikey - Create new and manage API Keys
  • deepsec_system_settings - Modify the system settings for TrendMicro Deep Security.
  • Docker Community Collection - community.docker 1.8.0 has been released with bugfixes and new features.
  • Community HashiVault Collection - community.hashi_vault 1.2.0 and 1.3.0 have been released. A new User Guide has also been published providing some detailed information about certain options.
  • Community General Collection - community.general 1.3.11, 2.5.4, and 3.3.0 (plus 3.3.1) have been released. The former two with bugfixes, and the latter with new features and bugfixes.
  • Community Sops Collection - community.sops 1.1.0 has been released, with a minor change to use public API from Ansible, and the addition of the decrypt filter.
  • Community RouterOS Collection - community.routeros 1.2.0 has been released.


The Ansible devel docsite will now always include the latest release version (the latest version that's not a prerelease according to semantic versioning) of all collections that will appear in the next Ansible release, instead of using exactly the same versions as the latest Ansible release. This means that devel for example includes community.hashi_vault 1.3.0, while the latest Ansible release available at time of writing (ansible-4.1.0) only contains community.hashi_vault 1.1.3. Also if community.hashi_vault 2.0.0 would have been released, it would be used for the devel docs, even if future Ansible 4.x.0 releases will only contain 1.y.z releases.

This allows collection developers and users to read documentation for the latest collection release, instead of just having docs for the latest release that's included in some Ansible version.

You can also see that the collection releases mentioned above - theforeman.foreman 2.1.1, community.routeros 1.2.0, and openstack.cloud 1.5.0 - are already documented on /devel/, while /latest/ contains older versions of these collections.


The following collections - community.mysql, community.postgresql, and community.proxysql - are looking for new maintainers and contributors! If you are interested, please refer to the corresponding pinned issues linked via the collection names.


  • Requesting review on gRPC connection plugin. This PR will add a new connection plugin for gRPC based communication with network hosts.
  • Requesting review on Platform agnostics network resource manager role for ansible.network collection.
  • Ansible has a new open source, data-centric, container-first, developer-friendly interface called ansible-navigator which will be included in the next Red Hat Ansible Automation Platform release. We are looking forward to your feedback, issues, and PRs in the repo. Please help us make this great!


Sebastian Gumprich wrote a blog post in German on how to convert roles into collections: Von einer Ansible-Rolle zur Collection – der weg ist das ziel.


Red Hat is hiring several roles to work on Ansible. Please check the job descriptions in the links and apply!


Thanks to everyone who participated in the Ansible Contributor Summit 2021.06 on June 8, 2021! We are slightly delayed with the editing of the recordings, and will have the videos and logs available in the Ansible Community wiki soon. In the meantime, please take a few minutes to fill in the Contributor Survey that we have put together.

The next Contributor Summit will take place alongside AnsibleFest. The dates are not confirmed yet, but it will be in the week of September 27, 2021. Details to follow!


Have any questions you’d like to ask, or issues you’d like to see covered? Please send us an email at the-bullhorn@redhat.com.