chore(deps): restrict helm provider version to ~ 2.0.0

[Benbentwo]

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

Summary by CodeRabbit

• Chores
  • Updated the Helm provider version constraint to restrict compatibility to the 2.x series in the Terraform configuration.

[coderabbitai]

Warning

Rate limit exceeded

@Benbentwo has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 10 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 9596501 and 284b6a7.

📒 Files selected for processing (1)

• src/versions.tf (1 hunks)

Walkthrough

The version constraint for the Helm provider in the Terraform configuration file was updated from ">= 2.0" to "~> 2.0", limiting provider versions to the 2.x series and preventing automatic upgrades to 3.x or higher.

Changes

File(s)	Change Summary
src/versions.tf	Updated Helm provider version constraint from ">= 2.0" to "~> 2.0".

Poem

A tweak to the Helm provider's line,
Now bound to two-dot-x, how fine!
No leaping to three, just steady and true,
Terraform scripts know what to do.
A hop, a skip, a version bound—
In rabbit code, safety is found!

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/versions.tf (1)

10-12: Good move to pessimistic constraint; consider an explicit lower bound for reproducibility

Switching from >= 2.0 to ~> 2.0 prevents an accidental upgrade to Helm provider 3.x—which is prudent.
If your module depends on features/fixes that were added later in 2.x (e.g., 2.11.0’s ARM‐template support), you might also pin a minimum patch/minor version:

helm = {
  source  = "hashicorp/helm"
  version = ">= 2.11.0, < 3.0.0"
}

This guarantees both forward-compatibility (no 3.x) and a consistent baseline across teams/CI runs.
Otherwise, the current change is perfectly acceptable.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 490f5b9 and 9596501.

📒 Files selected for processing (1)

• src/versions.tf (1 hunks)

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

• GitHub Check: component / terraform / Lint (./src)
• GitHub Check: component / terraform / bats
• GitHub Check: Summary

[github-actions]

These changes were released in v2.1.0.