Bullhorn #73

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #73, 2022-09-09 (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 said

MAJOR NEW RELEASES 🏆️

Antsibull 🐂

Tooling for building the Ansible package and collection documentation.

felixfontein shared

antsibull-docs 1.4.0 (changelog) has been released with new features and a bugfix. Installation instructions and collection links can now be customized, and error pages try to link to the collection's issue tracker instead of the collection's URL if possible.

COLLECTION UPDATES 🪄

felixfontein said

community.docker 3.1.0 (changelog) has been released with a new feature for community.docker.docker_swarm and some documentation improvements. The collection now also fully conforms to the REUSE specifications (except for the changelog fragments).

andersson007_ said

The community.mysql collection version 3.5.0 has been released! Special thanks to rsicart, betanummeric, laurent-indermuehle and aneustroev!

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!

COMMUNITY UPDATES 👂️

briantist contributed

galactory

galactory (an Ansible Galaxy proxy for Artifactory) has released version 0.4.0 with new support for configuration via config files and environment variables. Docker releases now include linux/arm64 arch images.

briantist shared

galactory version 0.5.0 has been released with new options for controlling the upstream proxy cache. With --cache-write=false it's now possible to proxy to an upstream without any writes to Artifactory, removing the need for an API key in some configurations.

steampunks contributed

Steampunk Spotter

Hey, our team has developed Steampunk Spotter, a tool that analyzes Ansible Playbooks and offers recommendations: https://steampunk.si/spotter/. You can try it out via CLI for free.

COMMUNITY EVENTS AND MEETUPS 📅

cybette contributed

Ansible Contributor Summit 2022.10

The Ansible Contributor Summit will be held the day before AnsibleFest 2022 on October 17, 2022, where participants will be able to join both in-person (in Chicago, IL, USA) and online.

We have put together a preliminary agenda, subject to change based on comments and feedback - and here's where we need your input! Please use the comment feature on hackmd to comment on the draft agenda, or propose additional topics in the planning hackmd. Alternatively you can ping me on matrix/irc with your comments and suggestions. Thanks!

THE ANSIBLE TEAM IS HIRING 💰️

gundalow said

Join the Ansible Controller Team

The Red Hat Ansible Controller Engineering team (which you may know as its upstream name, AWX, or old name of Ansible Tower) is looking for a Python Software Engineer to join us. In this role, you will add new functionality to and maintain released versions of automation controller by contributing to the design of new features, implementing features from designs, identifying root causes and fixing complex issues, assisting technical support with customer escalations, identifying and resolving gaps in the Continuous Integration (CI) pipeline, and developing needed enhancements. To succeed in this role, you’ll need to be friendly, curious, be willing to learn and teach, be sensitive to the perspectives of others, and care about creating a positive and inclusive environment. Successful applicants must reside in a state where Red Hat is registered to do business.

What you will do

  • Contribute to the design and perform the implementation of new features in automation controller
  • Troubleshoot customer-reported issues, guide in-house issue reproduction, determine root causes, describe issues in detail to fellow engineers and customers, and develop software code changes to resolve issues
  • Regularly communicate and interact with open source communities to provide guidance and understand issues; review community pull requests (PRs)
  • Work closely with technical support, documentation, and quality assurance (QA) teams to identify and deliver improvements to test automation, documentation, and knowledge base for automation controller
  • Develop and deliver customer-focused enhancements in maintenance releases
  • Investigate and recommend strategic improvements for tools and processes to advance and expand efficiency and throughput

Interested in helping us make Ansible Controller better? Apply now

cybette shared

Join the Ansible Community Team

The Red Hat Ansible Community team is looking for a Senior Software Community Engineer to join us!

In this role, you will work as part of a team focused on flourishing our amazing upstream community. The Ansible ecosystem is always growing and expanding. We want you to be part of the team that engages and keeps this community vibrant.

To find out more and apply, check out the job description. Note that this is a flexible Remote - global position, available in any country/state where Red Hat has a corporate presence.

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!