Update Terraform cloudposse/cloudfront-s3-cdn/aws to v0.93.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/cloudfront-s3-cdn/aws (source)	module	minor	0.92.0 -> 0.93.0

---

Release Notes

cloudposse/terraform-aws-cloudfront-s3-cdn (cloudposse/cloudfront-s3-cdn/aws)

v0.93.0

Compare Source

Fixed deprecated aws_s3_bucket attributes @​andruccho (#​293)

The following options were deprecated, and have either been updated, or replaced with the new necessary resources:

• server_side_encryption_configuration replaced with aws_s3_bucket_server_side_encryption_configuration resource
• versioning replaced with aws_s3_bucket_versioning resource
• cors_rule replaced with aws_s3_bucket_cors_configuration resource
• acl replaced with aws_s3_bucket_acl resource
• bucket_versioning input added

Pull request is almost the same with #​266, exclude override_json replaced with override_policy_documents option, because for me it breaks logs submodule behavior.
I'm getting no deprecation warnings without this change (my aws provider version is 5.30.0).

v0.92.1

Compare Source

🚀 Enhancements

Readme/example fix @​samcrudge (#​229)

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Example of 'Origin Group with the origin created by this module as a primary origin and an additional
  S3 bucket as a failover origin' showed the s3_origins & origin_group as a map(any) rather than a list(map) causing builds to fail when using said example.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Examples that reflect the required schema.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• README.md & README.yaml

🤖 Automatic Updates

chore(deps): update terraform cloudposse/iam-role/aws to v0.19.0 (main) @​renovate (#​271)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/iam-role/aws (source)	module	minor	0.16.0 -> 0.19.0

---

Release Notes

cloudposse/terraform-aws-iam-role (cloudposse/iam-role/aws)

v0.19.0

Compare Source

IAM Role name length limit @​&#​8203;goruha (#&#​8203;58)

what

• Fix IAM role name length limit

why

• Fix IAM role name length limited to 64

Sync github @​&#​8203;max-lobur (#&#​8203;54)

Rebuild github dir from the template

v0.18.0

Compare Source

• No changes

v0.17.0

Compare Source

Update main.tf @​&#​8203;karinatitov (#&#​8203;50)

have a chance to configure the name of the policy

what

• With this change i want to have an ability to provide a custom name for the policy

why

• the resources i'm working with were not created in the same way this module assumes
• to have a chance to configure the name of the policy

git.io->cloudposse.tools update @​&#​8203;dylanbannon (#&#​8203;46)

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

v0.16.2

Compare Source

🚀 Enhancements

Add enabled check to data source @​&#​8203;nitrocode (#&#​8203;45)

what

• Add enabled check to data source
• Add TestExamplesCompleteDisabled check

why

• Prevent creation if enabled is false

references

• https://github.com/cloudposse/terraform-aws-s3-bucket/pull/148

v0.16.1

Compare Source

🚀 Enhancements

Disabling all tags in all iam resources @​&#​8203;jamengual (#&#​8203;44)

what

• In https://github.com/cloudposse/terraform-aws-iam-role/pull/43 I added the option to disable role tags but in environments where roles are created under very strict controls, the policy tags for the roles sometimes can't be tagged. This change disable tags for all IAM related resources.

why

• to disable tags for role-related things. Use one variable instead of two.

references

• https://github.com/cloudposse/terraform-aws-iam-role/pull/43

---

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[undergrid-mergebot]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.

Terraform Plan 📖success

Show Plan

terraform
module.cdn.random_password.referer[0]: Refreshing state... [id=none]
module.cdn.data.aws_region.current[0]: Reading...
data.aws_s3_bucket.this: Reading...
module.cdn.module.logs.data.aws_caller_identity.current[0]: Reading...
module.cdn.data.aws_partition.current[0]: Reading...
module.cdn.module.logs.data.aws_partition.current[0]: Reading...
module.cdn.module.logs.module.aws_s3_bucket.data.aws_canonical_user_id.default[0]: Reading...
data.aws_route53_zone.this: Reading...
data.aws_acm_certificate.this: Reading...
module.cdn.aws_cloudfront_origin_access_identity.default[0]: Refreshing state... [id=E3OEDWFE328RRQ]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]
module.cdn.data.aws_partition.current[0]: Read complete after 0s [id=aws]
module.cdn.module.logs.data.aws_partition.current[0]: Read complete after 0s [id=aws]
module.cdn.data.aws_region.current[0]: Read complete after 0s [id=us-east-1]
module.cdn.module.logs.module.aws_s3_bucket.data.aws_partition.current[0]: Reading...
module.cdn.module.logs.module.aws_s3_bucket.data.aws_partition.current[0]: Read complete after 0s [id=aws]
module.cdn.module.logs.data.aws_caller_identity.current[0]: Read complete after 0s [id=072105303426]
module.cdn.module.logs.module.aws_s3_bucket.data.aws_canonical_user_id.default[0]: Read complete after 0s [id=0415ac49d2dbae53693985f648ef7b9ed41476f5aca8c9cafc28423e8d578bd3]
data.aws_s3_bucket.this: Read complete after 0s [id=kq4afy.xyz]
module.cdn.data.aws_s3_bucket.origin[0]: Reading...
module.cdn.data.aws_s3_bucket.origin[0]: Read complete after 0s [id=kq4afy.xyz]
module.cdn.aws_s3_bucket_public_access_block.origin[0]: Refreshing state... [id=kq4afy.xyz]
module.cdn.data.aws_iam_policy_document.s3_website_origin[0]: Reading...
module.cdn.data.aws_iam_policy_document.s3_website_origin[0]: Read complete after 0s [id=2431280419]
module.cdn.data.aws_iam_policy_document.combined[0]: Reading...
module.cdn.data.aws_iam_policy_document.combined[0]: Read complete after 0s [id=2431280419]
module.cdn.aws_s3_bucket_policy.default[0]: Refreshing state... [id=kq4afy.xyz]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket_versioning.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket_server_side_encryption_configuration.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket_public_access_block.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]
module.cdn.module.logs.module.aws_s3_bucket.data.aws_iam_policy_document.bucket_policy[0]: Reading...
module.cdn.module.logs.module.aws_s3_bucket.data.aws_iam_policy_document.bucket_policy[0]: Read complete after 0s [id=12357417]
module.cdn.module.logs.module.aws_s3_bucket.data.aws_iam_policy_document.aggregated_policy[0]: Reading...
module.cdn.module.logs.module.aws_s3_bucket.data.aws_iam_policy_document.aggregated_policy[0]: Read complete after 0s [id=12357417]
data.aws_acm_certificate.this: Read complete after 1s [id=arn:aws:acm:us-east-1:072105303426:certificate/b89f103c-57a2-4aa5-bd9c-bfed2eb09df0]
data.aws_route53_zone.this: Read complete after 1s [id=Z048504419NDW43VP1NZI]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket_policy.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]
module.cdn.module.dns.data.aws_route53_zone.default[0]: Reading...
module.cdn.aws_cloudfront_distribution.default[0]: Refreshing state... [id=E24XCU50JVWOD5]
module.cdn.module.logs.module.aws_s3_bucket.time_sleep.wait_for_aws_s3_bucket_settings[0]: Refreshing state... [id=2022-12-08T19:04:45Z]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket_ownership_controls.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket_acl.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]
module.cdn.module.dns.data.aws_route53_zone.default[0]: Read complete after 0s [id=Z048504419NDW43VP1NZI]
module.cdn.module.dns.aws_route53_record.ipv6["kq4afy.xyz"]: Refreshing state... [id=Z048504419NDW43VP1NZI_kq4afy.xyz_AAAA]
module.cdn.module.dns.aws_route53_record.default["kq4afy.xyz"]: Refreshing state... [id=Z048504419NDW43VP1NZI_kq4afy.xyz_A]
module.cdn.module.logs.module.aws_s3_bucket.aws_s3_bucket_lifecycle_configuration.default[0]: Refreshing state... [id=kq4afy-use1-cdn-logs]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: Terraform