ansible.utils VS community-topics

We're happy to announce the following networking collection updates: * ansible.utils 2.8.0 has been released with new features (changelog) * cisco.iosxr 4.0.3 has been released with bugfixes (changelog) * cisco.nxos 4.0.1 has been released with bugfixes (changelog) * junipernetworks.junos 4.1.0 has been released with new features (changelog)

The ipaddr filters are broken in ansible.netcommon 2.6.0 release as we have recently migrated ipaddr filters from ansible.netcommon to ansible.utils. We have released utils 2.5.2 and netcommon 2.6.1 which fixed these two issues (ansible.netcommon#375, ansible.utils#148). For the FQDN issue, the ansible-core team has already merged the fix. This fix will be available in the March 28th release, which means that users of non fqdn ipaddr filters can use the old netcommon collection version 2.5.1 as a workaround until the next ansible-core release (March 28th) by the core-team. For fqdn ipaddr filters, users can use the latest versions of any of ansible.netcommon (2.6.1) or ansible.utils (2.5.2).

We hope you'll enjoy part1 and part2, and take a look at the collection and source repo where we'd love to hear your suggestions on how to improve the collection.

Also handy for this and other IP related tests, the Ansible.utils collection https://github.com/ansible-collections/ansible.utils /u/CertifiedKnowNothing

See: https://www.ansible.com/blog/using-new-ansible-utilities-for-operational-state-management-and-remediation https://github.com/ansible-collections/ansible.utils/blob/main/plugins/sub_plugins/cli_parser/ttp_parser.py

Also, I've not done it this way, but I believe this could be short-cut even further using: https://github.com/ansible-collections/ansible.utils/blob/main/plugins/sub_plugins/cli_parser/ttp_parser.py#L23-L28

There is a community vote on a new policy for community.general on which ansible-core versions will be supported in new major releases. Basically support for ansible-core versions will be dropped if they were EOL at least a few weeks before the major release. For the upcoming community.general 8.0.0, that means that it will drop support for ansible-core 2.11 and 2.12 and require at least ansible-core 2.13. Details can be found in the associated issue.

As mentioned in The Bullhorn #113, we've opened a community / steering committee vote on declaring ngine_io.exoscale an effectively unmaintained collection and remove it from the Ansible 10 community package. Since then, there has been a new release. As a result, the vote ended with the decision to keep the collection in the community package.

2023-07-12: Community WG meeting, 18:00 UTC (propose topics here)

Hi everyone. We're working on making Ansible community documentation a separate project to ansible/ansible. The purpose is to benefit the Ansible community by decoupling community doc initiatives from core release cycles. This change also removes the Ansible Core team as the gate for other doc related efforts that will meet community needs, such as putting source content for docs.ansible.com under the direct control of the Steering Committee. Overall this change is a first step towards providing greater access and ownership of docs.ansible.com to the Ansible community.

Looking for your feedback on making community docs a separate github project to ansible/ansible, starting with moving /docs from ansible/ansible to ansible/ansible-documentation. See this issue for details.

It looks like the netapp.elementsw collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.elementsw for more information or to announce that you're interested in taking over the maintenance of (a fork of) netapp.elementsw.

The netapp.aws collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works.

As mentioned in The Bullhorn #98, we consider netapp.aws an effectively unmaintained collection. Therefore, we've opened a community / steering committee vote on removing it from the Ansible 10 community package.

2023-05-10: Community WG meeting, 18:00 UTC (propose topics here)

Work continues combining several pytest plugins for ansible.