community.aws VS news-for-maintainers

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

If you are using GHA to run tests on collections, you might have noticed strange failures when using ansible-test's --docker option when using ubuntu-latest. Read more about this and how to fix this in this issue.

In ansible/ansible, the stable-2.13 branch has been created (more infos), and the version of the devel branch has been bumped to 2.14.0.dev0 (more infos).

If you want to discuss this, we welcome feedback in ansible-collections/news-for-maintainers/discussions/4.

In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that has just been closed. To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page. If you do not want to get notifications about related discussions, please subscribe only to Issues. Please read the brief guidelines on how the repository should be used. Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!