chore: configure renovate to update opentofu itself, modules and providers

[gberenice]

what

These package rules will:

• Match both terraform providers and modules (matchDatasources)
• Use OpenTofu's registry URL (https://registry.opentofu.org) instead of the default Terraform registry
• This configuration will make Renovate look for updates in the OpenTofu registry for both providers and modules.
• This supports updating both Terraform and OpenTofu:
  • versions.tofu file will be updated using the OpenTofu registry
  • versions.tf file will be updated using the Terraform registry
  • Providers and modules in *.tf and *.tofu files will be updated using the OpenTofu registry

why

• Easier TF upgrades.

references

• INT-5003

Summary by CodeRabbit

• Chores
  • Updated Renovate configuration to support .tofu files and OpenTofu registry.
  • Added and upgraded linters in the lint configuration, including the latest Renovate linter and a newer version of Checkov.
  • Updated the standard registry version in the package management configuration.

[coderabbitai]

Walkthrough

This update introduces several configuration changes across project management and tooling files. The Renovate configuration now supports .tofu files alongside .tf files for Terraform, enabling dependency management for both Terraform and OpenTofu registries. New package rules have been added to distinguish between .tf and .tofu files, with appropriate registry assignments and dependency type handling. The linting configuration in .trunk/trunk.yaml has been updated by enabling the renovate@39.263.0 linter and upgrading the checkov linter version from 3.2.408 to 3.2.412. Additionally, the aqua.yaml configuration has been updated to reference the standard registry version v4.355.0 instead of v4.353.0. No changes were made to exported or public code entities.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 103adce and cc4b179.

📒 Files selected for processing (3)

• .github/renovate.json5 (2 hunks)
• .trunk/trunk.yaml (1 hunks)
• aqua.yaml (1 hunks)

🔇 Additional comments (7)

aqua.yaml (1)

11-11: Looks good - updated aqua registry version

The version reference for the standard registry was properly updated from v4.353.0 to v4.355.0, keeping the Renovate comment intact.

.trunk/trunk.yaml (2)

23-23: Good addition of Renovate linter

Adding the Renovate linter is appropriate and aligns with the PR objective of improving OpenTofu/Terraform dependency management. This will help ensure that the Renovate configuration is properly formatted and validated.

---

26-26: Looks good - updated Checkov version

The Checkov linter version has been appropriately upgraded from 3.2.408 to 3.2.412, keeping the infrastructure scanning capabilities up to date.

.github/renovate.json5 (4)

20-24: Great addition of .tofu file pattern to Terraform manager

This change properly extends the Terraform manager to watch both .tf and .tofu files, which is essential for the OpenTofu support mentioned in the PR objectives.

---

39-44: Good rule for routing provider and module updates to OpenTofu registry

This package rule correctly configures Renovate to use the OpenTofu registry (https://registry.opentofu.org) for all Terraform providers and modules in both .tf and .tofu files, matching the PR objective.

---

45-49: Appropriate configuration for .tofu required_version updates

This rule properly routes required_version dependencies in .tofu files to the OpenTofu registry, ensuring that version.tofu files will be updated using the correct source.

---

50-54: Correct configuration for .tf required_version updates

This rule maintains the use of the Terraform registry for required_version dependencies in .tf files, preserving compatibility with existing Terraform configurations while enabling OpenTofu support.

---

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

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.

[Gowiem]

Awesome