ansible-build-data VS ansible.utils

IBM -> RedHat -> Ansible (https://docs.ansible.com/platform.html)

I think the new ansible docs are opaque, and the new "everything is an ansible collection" scheme makes troubleshooting any issues reported by users hundreds of times harder than "the old days"

I keep this (https://github.com/ansible-community/ansible-build-data/blob...) bookmarked because it's the only way to match up what "ansible 8.1.0" (https://pypi.org/project/ansible/8.1.0/) even means since it for damn sure not any of this: https://github.com/ansible/ansible/releases (they used to have a 'release' pinned on that releases tab saying "these are not the droids you are looking for"). I believe I tried asking for them to update the completely erroneous pypi "source code" link to point to that repo and ... well, one can see how well that turned out

➡️ Check Release Notes📦️🗒️ and Ansible 8 Porting Guide for more details.

💽You can install it by running the following command or download the release tarball directly from pypi: pip install ansible==8.0.0a1 --user ➡️Check Release Notes 📦️🗒️ and Ansible 8 Porting Guide for more details!

You can find the current list for Ansible 7 here: https://github.com/ansible-community/ansible-build-data/blob/main/7/ansible-7.build

Check Release Notes📦️🗒️ and Ansible 6 Porting Guide for more details on changes, improvements, new and deprecated features!!

You can find the release announcement on ansible-announce and the changelog on GitHub. Happy automating!

The vmware.vmware_rest collection has been included in Ansible 5. Thanks to everyone involved!

As https://github.com/ansible-community/ansible-build-data/issues/114 showed we should really check the existing collections included in the Ansible package. Some ideas:

Ansible 5.7.0 has been released with updates to 19 of the included Ansible collections! Read the announcement or check out the update changelog to learn more about this new version.

Debian package "ansible" -> called "ansible" on PyPI -> is called "ansible collections" through most of the documentation -> upstream PyPI packages are generated through https://github.com/ansible-community/ansible-build-data

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