chore(deps): restrict aws provider version to < 6.0.0

[Benbentwo]

This pull request includes a version constraint update for the AWS provider in the Terraform configuration file src/versions.tf. The change ensures compatibility with versions up to but not including 6.0.0.

• src/versions.tf: Updated the version constraint for the aws provider to >= 4.9.0, < 6.0.0 to ensure compatibility with future versions while avoiding potential breaking changes in version 6.0.0.

Summary by CodeRabbit

• Chores
  • Updated AWS provider version constraints to allow versions from 4.9.0 up to, but not including, 6.0.0 in the Terraform configuration.
  • Upgraded the version of the "eks/alb-controller" component to improve compatibility and performance.

[coderabbitai]

Walkthrough

The AWS provider version constraint in the Terraform configuration was updated to specify both a minimum and a maximum version, now requiring versions >= 4.9.0 and < 6.0.0. Additionally, the "eks/alb-controller" component version in the vendor configuration was updated from v1.535.1 to v1.537.1.

Changes

File(s)	Change Summary
src/versions.tf	Updated AWS provider version constraint to add "< 6.0.0" upper bound
test/fixtures/vendor.yaml	Updated "eks/alb-controller" component version from v1.535.1 to v1.537.1

Poem

A tweak to the clouds, a version in hand,
Now AWS stands on a firmer land.
From 4.9 to just before six,
Our Terraform code avoids risky tricks.
The alb-controller got a little lift,
With v1.537, it’s a nifty gift! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc2045a and fe7d7d9.

📒 Files selected for processing (1)

• test/fixtures/vendor.yaml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• test/fixtures/vendor.yaml

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Summary

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

[goruha]

/terratest

[goruha]

/terratest

[goruha]

/terratest

[github-actions]

These changes were released in v1.536.2.