chore(deps): update terraform cloudposse/cloudfront-s3-cdn/aws to v2#61
chore(deps): update terraform cloudposse/cloudfront-s3-cdn/aws to v2#61renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
919d42f to
5c8b9fd
Compare
5c8b9fd to
39d0849
Compare
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
|
Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳ |
39d0849 to
08a0cb2
Compare
This PR contains the following updates:
1.1.1→2.1.1Release Notes
cloudposse/terraform-aws-cloudfront-s3-cdn (cloudposse/cloudfront-s3-cdn/aws)
v2.1.1Compare Source
feat: Enable additional CloudFront real-time metrics @jwadolowski (#372)
what
Add
additional_metrics_enabledvariable (default:falsefor backwards compatibility) that provisions anaws_cloudfront_monitoring_subscriptionresource when enabled.why
Not all CloudFront metrics are enabled by default. Some (4xx/5xx error rates by HTTP status code, origin latency, and cache hit rate) are hidden behind a monitoring subscription. This adds a convenient switch to enable them when needed.
The
realtime_metrics_subscription_statusvalue could have been derived fromvar.additional_metrics_enabled, but that would introduce an unexpected resource change across all existing deployments.references
A complementary PR to cloudposse/terraform-aws-cloudfront-cdn#162
docs: web acl id can be an ARN for newer WAFs @oycyc (#349)
As per the AWS provider docs. Updating description here so consumers don't get confused why WAF association fails when providing the ID.ID or ARN of the AWS WAF web ACL that is associated with the distribution. NOTE: If using the latest version of WAF (WAFv2), be sure to use the ARN. If using WAF Classic, use the ID. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_distribution#web_acl_id-3
v2.1.0Compare Source
feat: Add `response_completion_timeout` support @jwadolowski (#369)
what
response_completion_timeoutargument (announced by AWS in July 2025 and implemented in the 6.13.0 version of the AWS provider)>= 6.13.0why
Allows configuring
response_completion_timeoutfor CloudFront origins.references
v2.0.0Compare Source
chore: fix "name" deprecation for aws_region data source @morremeyer (#363)
what
This fixes the deprecation of the "name" attribute for the aws_region data source, adding a fallback for provider versions < 6.0.0.
why
To get rid of the deprecation notice and prepare for provider version 7.
references
Resolves #361.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.