Skip to content

v0.24.2
Compare
Choose a tag to compare
@cloudpossebot cloudpossebot released this 26 Aug 20:43
0.24.2
43b5746
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
enable http3 @kevcube (#90)

what

  • Enable HTTP/3 support in CloudFront

why

  • It's faster, and shinier than http/2

references

git.io->cloudposse.tools update @dylanbannon (#87)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

  • DEV-143

🤖 Automatic Updates

Update Terraform cloudposse/route53-alias/aws to v0.13.0 @renovate (#81)

This PR contains the following updates:

Package Type Update Change
cloudposse/route53-alias/aws (source) module minor 0.12.1 -> 0.13.0

Release Notes

cloudposse/terraform-aws-route53-alias

v0.13.0

Compare Source

BREAKING CHANGE: Because this release changes resource addresses, it will result in Terraform destroying and recreating some resources. Please consider removing aws_route53_record resources from the state and importing them to the new resource addresses if you do not with for any destructive changes.

Fix: Add BridgeCrew Suppressions @​korenyoni (#​39) ##### what
  • Add BridgeCrew suppressions
why

Add suppressions appearing in #​37

CleanShot 2022-01-27 at 23 08 27@​2x ##### references * #​37
Chore: Run 'make github/init' @​korenyoni (#​38) ##### what * Run `make github/init` ##### why * Updates GHA-workflow-related files to their latest distribution in https://github.com/cloudposse/build-harness * Allows using `no-release` label for consolidating multiple PRs into a single release. ##### references * N/A
##### 🐛 Bug Fixes
Fix: create records using `for_each` instead of `count` @​1david5 (#​37) ##### what * Modify `default` and `ipv6` `aws_route53_record` resources to use `for_each` instead of `count`. ##### why * Prevent destroying and recreating DNS records when removing elements from `aliases` list.
Update Terraform cloudposse/s3-log-storage/aws to v0.26.0 @renovate (#71)

This PR contains the following updates:

Package Type Update Change
cloudposse/s3-log-storage/aws (source) module minor 0.24.1 -> 0.26.0

Release Notes

cloudposse/terraform-aws-s3-log-storage

v0.26.0

Compare Source

Add S3 bucket ownership controls @​max-lobur (#​61) #### what * Set aws_s3_bucket_ownership_controls to BucketOwnerPreferred #### why * Per [docs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html) this setting will let object uploader decide ownership. If `bucket-owner-full-control` ACL is specified, the bucket account take ownership, otherwise the writer account keeps ownership. Bucket on its side may enforce presence of the `bucket-owner-full-control` ACL which we already do when needed. So this setting was the only missing piece to make ownership work like we expected * I found no use cases for the other value of this resource: `ObjectWriter`. It corresponds to legacy S3 behavior which was broken for us. Decided to always set to `BucketOwnerPreferred` and not allow to customize. If the owner must be preserved, we should not pass `bucket-owner-full-control` - this is a more clear way to control the behavior. #### references * https://aws.amazon.com/blogs/storage/enforcing-ownership-of-amazon-s3-objects-in-a-multi-account-environment/ * https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html * https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_ownership_controls#ObjectWriter

v0.25.0

Compare Source

Add support for bucket notifications @​max-lobur (#​60) #### what * Add support for bucket notifications * Only SQS destination for now #### why * To enable log collection

Contributors

kevcube, renovate, and dylanbannon
Assets 2
Loading