Bullhorn #80

Source

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #80, 2022-11-04 (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!

KEY DATES ⏱️

cybette shared

GENERAL NEWS UPDATES 🔈️

gotmax (He/Him) contributed

The weekly community meeting has moved from Wednesdays at 18:00 UTC to Wednesdays at 19:00 UTC so it stays at 2:00 p.m. EST / 8:00 p.m. CET now that DST / summer time is ending. The meeting location -- #ansible-community on IRC and #community:ansible.com on Matrix -- remains the same. As always, all interested community members are welcome!

samccann said

Ansible 2.3 docs have moved to the archive site at https://docs.ansible.com/archive/ansible/2.3/. Update any bookmarks you have as old bookmarks will now redirect to /latest/ documentation.

MAJOR NEW RELEASES 🏆️

john-westcott-iv shared

We're happy to announce that the next release of AWX, version 21.8.0 is now available! Some notable features include: * Adding ppc64le support parameters * Shortcut Instance.objects.me when possible * Hostname validation in InstanceSerializer * Update UI to support pending health checks. * Sending field_name in AttributeError * Allows job output to calculate elapsed time * Make job lifecycle Cyan again * Add arm64 architecture mapping to image_architecture for m1mac * Allows health checks on only execution nodes

In addition AWX Operator version 1.0.0 has also been released! Some notable features include: * Change no_log type to boolean * Enable configuration of route and ingress api versions

Please see the release pages for more details: AWX: https://github.com/ansible/awx/releases/tag/21.8.0 Operator: https://github.com/ansible/awx-operator/releases/tag/1.0.0

Known Issues: * In AWX Operator the no_log property has changed from a string to a boolean.

COLLECTION UPDATES 🪄

briantist contributed

community.hashi_vault version 3.4.0 has been released with a new module and bugfix. This is the last expected 3.x.y release before 4.0.0.

felixfontein contributed

community.docker 3.2.0 (changelog) has been released with a new feature and two deprecations in docker_container.

felixfontein said

community.general 6.0.0-a1 (changelog) has been released. This is a pre-release for the upcoming 6.0.0 major release. The main objective of this pre-release is to make it possible to test the large stuctural changes by flattening the directory structure. See the corresponding entry in the changelog for details.

andersson007_ said

community.network collection 5.0.0 has been released! See the changelog for details. Special thanks to felixfontein for removing flat-mapping and other improvements!

Im0 contributed

collection.rabbitmq has released version 1.2.3 which is available on github and galaxy. More details are available within the changelog.

felixfontein shared

community.crypto 2.8.0 (changelog) has been released with some new features. The openssl_pkcs12 module allows to select an encryption level with recent enough cryptography libraries, and there have been further improvements for the ACME modules with regard to error handling.

hunleyd said

The community.postgresql team has released 1.7.6 as a bugfix release.

hunleyd shared

The community.postgresql team has released the 2.3.0 minor release. Thanks to all those involved!

HELP WANTED 🙏

andersson007_ shared

The following collection inclusion requests are waiting for your review:

See the process description to learn how to do it.

If you have any questions, just ping andersson007 on Matrix in the #community:ansible.com room or on Libera.Chat IRC in the #ansible-community channel or directly.

Please help the community extend the Ansible package!

PROPOSALS - DISCUSS AND VOTE! 🗳️

gotmax (He/Him) said

The community steering committee has started a vote on whether we should amend the Ansible community package removal process to consider collections with unresolved Collection Requirements violations unmaintained and thus subject to removal. Please see the PR that amends the policy and the community-topics ticket for more information.

COMMUNITY UPDATES 👂️

Gwmngilfen contributed

Summit review time! Speaking as the data person for the Ansible Community Team, Contributor Summit (and AnsibleFest overall) looks to have been quite popular!

Typically we might see ~20-25 unique accounts / day in our Social room (and the Summit room is obviously very quiet outside of events). However, we saw over 100 people in those two rooms during Contributor Summit, and sustained over 50 during the Fest keynotes as well. In total we saw well over 200 unique accounts during the week.

We also saw almost 100 new folks join the Social room over the course of the keynotes (and the rest of the week), for which thanks again to maxamillion and cybette for the keynote and interview shoutouts. We hope you're enjoying it!

As usual, I'll have the survey out shortly, which is open to all the community (whether you attended Summit or not). I look forward to making even more plots for your comsumption 🙂

steampunks contributed

Steampunk Spotter version 1.1 has been released! The new version of this tool that analyzes Ansible Playbooks brings new checks for simplified Ansible upgrades, GitLab integration, and quick reference to Ansible module documentation for the entire Ansible Galaxy.

COMMUNITY EVENTS AND MEETUPS 📅

gundalow shared

The Ansible London in-person Meetup returns!

After a long break, the London Meetup resumes on Wednesday 14th December.

We will have talks on

  • chocolatey - The Package Manager for Windows
  • Adopting systems compliance using CIS - Remediation and Audit

RSVP to reserve your seat.

gundalow contributed

New Meeting: AWX Office Hours

One of the many benefits of open source projects is the ability to form – and collaborate with – a community of users and contributors. This mutually benefits the project and the community at large: it helps the project stay pertinent to its users (who can first-hand voice their opinions and concerns) and it helps users to gain insight into the overall direction of the project which makes it easier to know what to expect in the future. All the while, contributors are able to implement features, enhancements, and documentation that they themselves consider important.

This kind of feedback loop is vital to the success of AWX and the AWX team wants to make it as easy as possible for you - our community - to get involved. To that end, we have several things in the works, and would like to begin by announcing our new AWX Office Hours meeting.

Our first meeting will be held on Tuesday, November 8, 2022 at 1500 UTC on Google Meet.

Add the topics you are interested to AWX Office Hours Agenda.

THE ANSIBLE TEAM IS HIRING 💰️

Don Naro said

We're hiring! The Ansible team at Red Hat is looking for an Automation Engineer who loves automating repetitive tasks, diving deep into source code and systems to perform root-cause analysis of issues. Apply to the Software Quality team at this link or share with someone you know.

Don Naro contributed

Another exciting opportunity to join the Ansible team at Red Hat. We're looking for someone who constantly looks for ways to break things and rebuild them better. Come and join the Quality Engineering team as a developer who designs and automates creative ways to break software and uncover problems. Apply to the role at this link or share with someone you know.

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!

Powered by