We want to hear from you! Help us gain insights into the state of the Ansible ecosystem.
Take the Ansible Project Survey 2024

Bullhorn #92

Source

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #92, 2023-02-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!

KEY DATES ⏱️

cybette contributed

GENERAL NEWS UPDATES 🔈️

Gwmngilfen shared

Community strategy 2023 - have your say!

In recent weeks, the Red Hat Ansible Community Team has been writing up the state of the community in 2023, the issues that we see, and what we think we should do about it. I'm happy to announce that this is now live for your comments, questions, and votes.

This takes the form of two blog posts:

I also presented this strategy at the Ansible Contributor Summit two weeks ago in Ghent, so if you'd like to see that, head over to YouTube for the recording.

In short, we believe the time has come to have a community DNS zone separate to ansible.com, and also to have a project-wide discussion space in the form of a Discourse forum. Crucially though, we don't get to call all the shots - so if you have opinions, or just want to give it a thumbs-up, you can head to the GitHub discussions part 1 & part 2.

See you in the discussion!

MAJOR NEW RELEASES 🏆️

DevTools ↗ ⛏️

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

Priyam Sahoo shared

  1. Ansible-lint 6.13 introduces a new feature that allows users to utilize a .ansible-lint-ignore file. This file contains skip-rules that are loaded from the ignore file which is adjacent to the config file. Additionally, users can take advantage of the --generate-ignore argument to dump any current violations into an ignore file.

  2. The Devtools team has just released a stable update for vscode-ansible extension, version 1.2.44, packed with important bugfixes and 2 exciting features:

  3. First addition is the information regarding a newer version ansible-lint availabilty in the status-bar itself. This ensures that users always have access to the most up-to-date tools and can stay ahead of the curve.
  4. Secondly, the update includes a feature that enables Red Hat telemetry gathering. This feature allows users to contribute to the ongoing development of the extension, ensuring that the tool remains cutting-edge and effective.

ssbarnea said

DevTools team made a pre-release of ansible-lint 6.14 which drops support for python 3.8 and includes 7 important bugfixes.

PROJECT UPDATES 🛠️

Sagar Paul said

A few updates on what the Networking team is working on: * we are developing some content related to interfaces and ospf * we are working on extending the capabilities of nxos_bgp_global to support the creation of neighbour templates; earlier we could use the module to just apply one that is already created * we are planning to release a filter plugin (ace_popper) which acts on a set of acls facts gathered from a network appliance, and removes ace entries on the basis of some matching criteria

COLLECTION UPDATES 🪄

felixfontein shared

community.crypto 2.11.0 (changelog) has been released with a new feature and some bugfixes.

adhawkins contributed

New version of the adhawkins.borgbase collection v1.0.2 includes some minor fixes regarding parameter types to borgbase_repo.

PROPOSALS - DISCUSS AND VOTE! 🗳️

andersson007_ said

As the concerns about the future of the Ansible package continue to show up, the Community-approved collections instead of collection inclusion? community topic has been created. Please share your thoughts!

Felix Fontein contributed

Some time ago we started a community discussion on how to mark plugins in a collection as private. Since ansible-core rejected to implement support for this in the ansible-doc CLI tool, I'm proposing to still standardize this so we can at least implement it in the community tooling, in particular antsibull-docs and antsibull-changelog. Please see my call to action for how to continue for details. If you are interested in this, please use the discussion issue to voice your opinions on this.

dmsimard contributed

Do you have experience with Prometheus and Ansible?

ARA Records Ansible playbooks and it has a bunch of information and metrics about tasks, hosts and results.

What should a prometheus exporter to get Ansible metrics out of ara look like?

What kind of queries or monitoring would you like to do?

Your help and feedback would be appreciated!

Reach out on Mastodon or see this issue on GitHub.

Felix Fontein said

More than two years ago the Ansible Docs Working Group started discussing the use of semantic markup for Ansible plugin/module documentation. This resulted in a specification that has been implemented as proofs of concept both for ansible-doc and the validate-modules sanity test, as well as for antsibull-docs. From the docs perspective this will improve plugin, module, and now also role documentation a lot, and in particular separate markup from content. (Right now you have to use C(...) and I(...) for values and option names, which stand for 'code-style' and 'italics'.)

Unfortunately this has been on hold for a long time since changes to documentation now require approval of various Ansible-related projects. Since it is still unclear when/if this will ever continue, I am proposing to start implementing this on the community side, i.e. antsibull-docs, so community collections can try to start playing around with this, which will hopefully put some pressure on other projects to move the semantic markup proposal forward. Please use the associated discussion issue in community-topics to voice your opinions on this.

HELP WANTED 🙏

Don Naro shared

Are you interested in helping improve the navigation and layout of "docs.ansible.com"? Do you think you can help connect users with information in the docs more efficiently? If so, the Ansible community team invites you to contribute to this repository. We plan to use this repository to overhaul the landing pages for Ansible community documentation and create a more intuitive and modern user experience. See you in the PR queue!

samccann said

Looking to help out in Ansible but not sure where to start? Take a look at some easyfix or good first issues: * across multiple collections * for all other Ansible projects

COMMUNITY UPDATES 👂️

steampunks shared

Steampunk Spotter and Ansible Lint - it’s not about how they differ, but how they complement each other. Using both tools is a winning combination and guarantees reliable automation you can trust.

COMMUNITY EVENTS AND MEETUPS 📅

anwesha said

We are having the first-ever Ansible Community Day India on 25th February 2023, i.e. tomorrow. It is a whole-day in-person community event with talks, workshops, and BoF sessions. Learn about the Ansible project and community, and share the story of your Ansible journey with us. We are excited to welcome you all tomorrow. Also join us in the Ansible Contributor Summit Matrix room during the event to chat (we recommend the Element Web for a Matrix client).

You can get to know more about the event at the Meetup page.

cybette shared

Ansible München is having their 1st Ansible Meetup of the year on Feb 28 @ 18:00 CET. There will be 2 talks: "On-Containerized Ansible" by Guillermo Gomez and "Build Sovereign Cloud with Ansible" by Danny Afahounko. RSVP and attend!

cybette said

Ansible Zürich will also be having an event on Feb 28 @ 17:00 CET, as their 12th Ansible Meetup. They have planned 3 topics: "Ansible LFOps - What's new in v2.0", "Getting started with Ansible Navigator", and "Ansible Sewing Box". RSVP and attend!

cmrussell99 contributed

Join the next office hours call on Event-Driven Ansible! We share tips and techniques and most importantly answer your questions as you try Event-Driven Ansible. Next call is on March 2, 2023 at 11AM ET. Register here.

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