chore(deps): update terraform cloudposse/utils/aws to v1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	major	0.8.1 -> 1.4.0

---

Release Notes

cloudposse/terraform-aws-utils (cloudposse/utils/aws)

v1.4.0

Compare Source

Add il-central-1 region @​jasonmk (#​31)

what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references

Sync github @​max-lobur (#​27)

Rebuild github dir from the template

v1.3.0

Compare Source

• No changes

v1.2.0

Compare Source

Add 4 regions: aps2, apse4, euc2, eus2 @​Nuru (#​26)

what

Add 4 newest regions:

1. "ap-south-2" = "Asia Pacific (Hyderabad)" (Note: fixed code is ar2 because as2 is taken by ap-southeast-2)
2. "ap-southeast-4" = "Asia Pacific (Melbourne)"
3. "eu-central-2" = "Europe (Zurich)"
4. "eu-south-2" = "Europe (Spain)"

• Add all_regions output
• When testing, check to make sure all regions have abbreviations

why

• Provide full coverage.

references

• Closes #​24
• Supersedes and closes #​25

🤖 Automatic Updates

Update framework @​cloudpossebot (#​23)

what

This is an auto-generated PR that updates the README.md and docs that has been enhanced to update other framework elements such as workflows and test code

why

To have most recent versions of the framework elements

v1.1.0

Compare Source

Add me-central-1, ELB Logging S3 Bucket Policy, Local Zones, Display Names @​Nuru (#​21)

what

• Add new me-central-1 zone
• Add missing Local Zones from us-east-1 and us-west-2
• Add ELB Logging S3 Bucket Policy output
• Add region display name map
• Update minimum Terraform version to 0.14.0

why

• Maintain complete coverage of regions
• Improve coverage of local regions
• To enable ELB access logging to an S3 bucket, you have always needed a region-specific bucket policy. This module provides the account number to use in a policy template based on region, but that is no longer sufficient. There are now 3 different templates for S3 bucket policies, and again which one to use depends on the region. Therefore, to further simplify the task for others, this module can output the full policy JSON, not just the account number.
• There is no official API to convert from the official region name, like eu-north-1, to a human-friendly name, like "Europe (Stockholm)". This module now outputs a map of such names, derived from the AWS Java SDK.
• Previous minimum Terraform version 0.13.0 has different formatting, causing formatting checks to fail when compared to code formatted by later versions

references

• https://aws.amazon.com/blogs/aws/now-open-aws-region-in-the-united-arab-emirates-uae/
• https://github.com/aws/aws-sdk-java/issues/1467
• Supersedes and closes #​18
• Supersedes and closes #​19

v1.0.0: Initial release with production Semantic Versioning

Compare Source

Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules. The only substantive change between this version and the previous version (0.8.1) is the addition of support for the new ap-southeast-3 region (Jakarta).

🚀 Enhancements

Add ap-southeast-3 to regions supported @​Benbentwo (#​17)

what

• Adds ap-southeast-3 support

why

• Jakarta Support

Update README and framework @​dylanbannon (#​16)

what and why

• Update README to cover new features
• Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.
• Update test framework to current

References

• DEV-143

---

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 was generated by Mend Renovate. View the repository job log.

[mergify]

/terratest

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟠 Require terratest

Waiting checks: test/terratest.

This rule require terratest status

• check-success = test/terratest

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳

[mergify]

Heads up! This pull request looks stale. It will be closed soon, if there are no new commits. ⏳