6.5.6

What's Changed

• Use aws_s3_bucket_policy resource by @legoscia in #27

Full Changelog: 6.5.5...6.5.6

6.5.5

What's Changed

• Use aws_s3_bucket_website_configuration resource by @legoscia in #26

Full Changelog: 6.5.4...6.5.5

6.5.4

What's Changed

• Remove ignore_changes block by @legoscia in #25

Full Changelog: 6.5.3...6.5.4

6.5.3

What's Changed

• Fix response_headers_policy_id not being propagated by @ddosia in #24

Full Changelog: 6.5.2...6.5.3

6.5.2: Make http_version configurable (#23)

Allow enabling HTTP/3.

6.5.1: Add option for creating AAAA record in r53-alias module (#22)

The site-main and site-redirect modules already support IPv6 (and
r53-cname doesn't need to do anything special), so let's add the
missing piece of the puzzle.

6.4.3: Add "ignore changes" rule for S3 bucket (#20)

This is recommended in the documentation for the Terraform AWS
provider, versions below 4.9.0, e.g.:
https://registry.terraform.io/providers/hashicorp/aws/3.75.0/docs/resources/s3_bucket_lifecycle_configuration#usage-notes

This should put an end to S3 bucket configurations changing back and
forth, when an additional Terraform resource is being used.

6.4.2

Support setting a response headers policy for cache behaviors (#19)

6.4.1: Support configuring a WAF web ACL (#18)

This makes it possible to use WAF to block certain requests to the
Cloudfront distribution.

6.2.3: Custom User-Agent header is optional (#12)

If the parameter is the empty string, omit the custom User-Agent
header.

We only need this for S3 origins, not for services such as querytool,
for which it might be useful to see the original User-Agent header.