Skip to content

amazon.aws 7.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 Dec 07:12
· 867 commits to main since this release
7.1.0
This tag was signed with the committer’s verified signature.
tremble Mark Chappell
GPG key ID: DB59B921BD88730F
Verified
Learn about vigilant mode.
3801882
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Release Summary

This release brings some new features and several bugfixes.

Minor Changes

  • autoscaling_group - minor PEP8 whitespace sanity fixes (#1846).
  • ec2_ami_info - simplify parameters to get_image_attribute to only pass ID of image (#1846).
  • ec2_eip - use ResourceTags to set initial tags upon creation (#1843)
  • ec2_instance - add support for AdditionalInfo option when creating an instance (#1828).
  • ec2_security_group - use ResourceTags to set initial tags upon creation (#1844)
  • ec2_vpc_igw - use ResourceTags to set initial tags upon creation (#1843)
  • ec2_vpc_route_table - use ResourceTags to set initial tags upon creation (#1843)
  • ec2_vpc_subnet - the default value for tags has been changed from {} to None, to remove tags from a subnet an empty map must be explicitly passed to the module (#1876).
  • ec2_vpc_subnet - use ResourceTags to set initial tags upon creation (#1843)
  • ec2_vpc_subnet - use wait_timeout to also control maximum time to wait for initial creation of subnets (#1848).
  • iam_group - add support for setting group path (#1892).
  • iam_group - adds attached_policies return value (#1892).
  • iam_group - code refactored to avoid single long function (#1892).
  • rds_instance_snapshot - minor PEP8 whitespace sanity fixes (#1846).

Bugfixes

  • ec2_vpc_subnet - cleanly handle failure when subnet isn't created in time (#1848).
  • s3_object - Fix typo that caused false deprecation warning when setting overwrite=latest` (#1847).
  • s3_object - when doing a put and specifying Content-Type in metadata, this module (since 6.0.0) erroneously set the Content-Type to None causing the put to fail. Fix now correctly honours the specified Content-Type (#1881).
Assets 2
Loading