ansible.utils VS amazon.aws

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

amazon.aws 6.4.0 has been released with a new module named amazon.aws.ec2_key_info, some documentation improvements, new features and bugfixes (see changelog for details).

amazon.aws 5.5.1 has been released with several bugfixes (see changelog for details).

amazon.aws 5.5.0 has been released with a number of bugfixes, new features and new modules. This is the last planned minor release prior to the release of version 6.0.0 (see changelog for details).

amazon.aws 5.4.0 has been released with bugfixes for the ec2_metadata_facts, ec2_vol, rds_instance and route53_info modules, as well as feature enhancements for the ec2_spot_instance and route53_health_check modules - see changelog for details.

Hi folks! I'm one of the docs writers for community Ansible (aka docs.ansible.com, not access.redhat.com). It sounds like you've found a place to log your docs problems already but I did open an issue on the amazon.aws collection directly to handle the examples that aren't quoted for `filters` at https://github.com/ansible-collections/amazon.aws/issues/1331

The amazon.aws collection version 5.0.0 has been released. See the changelog for details on new modules and features.

amazon.aws 4.0.0 has been released with some new features, bugfixes, breaking changes and deprecated features. The amazon.aws collection has also dropped support for botocore<1.20.0 and boto3<1.17.0 (see changelog for details).

amazon.aws 2.2.0 has been released with bug-fixes (see changelog for details).

amazon.aws 3.1.1 has been released with some new features, bugfixes and a deprecation (see changelog for details). 3.1.0 failed to publish on Galaxy, hence, we had to bump the release version.

The AWS community has begun planning for the 4.0.0 releases of amazon.aws and community.aws. Please see the linked issues for more details or to get involved.