community.aws VS ansible.netcommon

community.aws 6.0.0 has been released with some new plugins and features. Several bugfixes, breaking changes and deprecated features are also included. The community.aws collection has dropped support for botocore<1.25.0 and boto3<1.22.0. Support for Python 3.6 has also been dropped (see changelog for details).

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

community.aws 3.2.1 has been released. The new parameter purge_tags in ec2_asg module, that was introduced in community.aws 3.2.0 with its default value true, possibly breaks existing playbooks for users if they don't update their playbooks and specify purge_tags: false. However, this release restores the previous behaviour.

community.aws 3.2.0 has been released with some new features and bugfixes (see changelog for details).

community.aws 3.1.0 and 2.3.0 have been released.

Related to that, the ansible "community.aws.aws_ssm" connection plugin[0] always returns the output of "raw:" tasks with "\r" appended to it, too, and I'd guess it's for a similar reason

0: https://github.com/ansible-collections/community.aws/blob/3....

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.

ec2_instance information using this module -> community.aws.ec2_instance_info_module

ansible.netcommon has been released with bugfixes (changelog).

ansible.netcommon 5.0.0

Would you share the version of netcommon/ ansible-core version installed for you? and please file an issue here, https://github.com/ansible-collections/ansible.netcommon/issues. Regards

There have been a few networking releases this week: * ansible.netcommon 3.1.0 has been released with new features (changelog) * cisco.ios 3.3.0 has been released with new features (changelog) * cisco.iosxr 3.3.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).

This also affected net_get. New pull request to address this: https://github.com/ansible-collections/ansible.netcommon/pull/199