The #Ansible Bullhorn #227 is out!This week's highlights include:- Paramiko deprecated for network_cli.- AWX modernization: Ansible Jewel proxy layer.- ai-forge content development skills update.- 6 collection updates - check the newsletter for the full list.Read more: https://forum.ansible.com/t/the-bullhorn-227/45785#OpenSource #Automation

The #Ansible Bullhorn #226 is out!Highlights: Ansible UI returns to upstream development, AWX modernization update, cisco.ucs ACP requirements violation, and clarifying ansible-test for collection testing.Plus new Ansible-Core, Antsibull and Ansible Community Package releases.New collection updates too.Read more: https://forum.ansible.com/t/the-bullhorn-226/45764#OpenSource #Automation

The #Ansible Bullhorn #225 is out!This week's highlights include:- Ansible and the EU Cyber Resilience Act.- New Ansible-Core and Ansible Community Package releases.- 9 collection updates - check the newsletter for the full list.- Discussions around documenting breaking changes in collections.- The Ansible Community AI Policy Proposal.Read more: https://forum.ansible.com/t/the-bullhorn-225/45736#OpenSource #Automation #IaC

The #Ansible Bullhorn #223 is out!Highlights: Ansible AI collaboration repository, New CI requirement for included collections, and Ansible playbook scanning tools.Plus new Ansible-Core and Ansible Community Package releases.New collection updates too.Read more: https://forum.ansible.com/t/the-bullhorn-223/45608#OpenSource #Automation

Latest edition of the #Ansible bullhorn is out! With collection updates and Red Hat Summit details!https://forum.ansible.com/t/the-bullhorn-220/45497

The latest edition of the Ansible Bullhorn 219 is out! https://forum.ansible.com/t/the-bullhorn-219/45456It shares the release updates about ansible core and ansible community package, news about certified collections and events & meetups in the Ansible land.

Yay! @ddev support for ce-provision #Ansible development! https://gitlab.com/code-enigma/ce-provision/-/merge_requests/2934#DDEV #Docker

@badnetmask @davdr The really sad thing is that I could solve it with a couple of lines shell-script. Maybe I should just print out a note at the end of the ansible run to do so.