community.postgresql VS ansible.utils

The community.postgresql collection released a new version: 3.2.0.

We are happy to announce that the community.mysql collection has found a new maintainer: Felix Hamme (betanummeric on GitHub/Matrix)! He's also already a maintainer of the community.postgresql collection and has a great history of contributions in both. Thanks, Felix, and welcome to the crew!:)

The community.postgresql collection has released two new version: 1.7.9 and 2.4.1. They revert the breaking change accidentally introduced in the previous version (which was intended for a later major release).

The community.postgresql collection version 2.3.1 has been released (changelog). Thanks to vonschultz and hunleyd!

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

We are also happy to announce a new maintainer of the community.postgresql collection - Felix Hamme (betanummeric on GitHub)! Our congratulations, Felix, and thank you for your great contribution in many collections and desire to help!

The community.postgresql maintainers need your feedback! A proposal for formalizing the supported PG versions has been filed here and needs your input. If adopted, the collection will issue major releases yearly and each major release will officially support the five major version of PG supported at that time. We think this will ultimately improve the collection and improve the end user's experience but we need your input. We look forward to hearing from everyone!

Recently, we opened https://github.com/ansible-collections/community.postgresql/issues/276 to discuss formalizing the supported PostgreSQL versions in the community.postgresql collection. This is a big change for the collection and we want to ensure the proposal makes sense for the collection's users. If you use the collection, please review the proposal and add your thumbs up/down, comment, etc. Thanks!

The community.postgresql collection has released 1.7.3 and 2.1.4 to fully deprecate Ansible 2.9/2.10. Thanks to our newest contributor jchancojr and everyone else involved!

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