Align with Infracost tagging policies

[brettcurtis]

Summary by CodeRabbit

• Documentation

  • Updated the README to reflect new versions for the google provider and the project module.

• Refactor

  • Enhanced label management in Terraform configuration for clearer semantic meaning.

• Chores

  • Updated the pre-commit-terraform hook to a newer version for improved functionality.

• New Features

  • Introduced CodeRabbit configuration for advanced features such as request changes workflow, auto review, and chat auto-reply.

[infracost]

Infracost report

💰 Monthly cost will not change

Cost details

──────────────────────────────────

111 cloud resources were detected:
∙ 3 were estimated, all of which include usage-based costs, see https://infracost.io/usage-file
∙ 99 were free, rerun with --show-skipped to see details
∙ 9 are not supported yet, rerun with --show-skipped to see details

Governance checks

🟢 50 passed

48 FinOps policies, 1 Tagging policy, and 1 Guardrail passed.

_{View in Infracost Cloud. This comment will be updated when code changes.}

[coderabbitai]

Walkthrough

The recent changes involve upgrading versions for the Google provider and the project module in the Terraform configuration, enhancing compatibility and potentially introducing new features. Additionally, improvements have been made to the configuration by redefining and expanding labels, enhancing the infrastructure's semantic clarity. The update to pre-commit hooks for Terraform likely offers improved linting and validation capabilities to streamline development workflows.

Changes

File(s)	Change Summary
.global/infra/README.md	Updated google provider version from 5.8.0 to 5.17.0; project module version from v0.1.8 to v0.1.9.
.global/infra/main.tf	Updated label definitions, including renaming and adding new labels.
.pre-commit-config.yaml	Updated pre-commit-terraform version from v1.83.6 to v1.88.0.
.coderabbit.yaml	Introduces configuration settings for CodeRabbit, enabling early access features like request changes workflow, auto review, and chat auto-reply functionality.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between d6df599 and 695cdb3.

Files selected for processing (3)

• .pre-commit-config.yaml (1 hunks)
• global/infra/README.md (1 hunks)
• global/infra/main.tf (1 hunks)

Files skipped from review due to trivial changes (1)

• global/infra/README.md

Additional comments: 2

.pre-commit-config.yaml (1)

• 24-24: The update of the pre-commit-terraform repository version to v1.88.0 aligns with the PR objectives. Ensure to review the release notes of v1.88.0 to leverage any new features or improvements that could benefit the project.

global/infra/main.tf (1)

• 54-57: The updates to the labels in the Terraform configurations align with the PR objectives to improve clarity, consistency, and alignment with the Infracost tagging policies. Ensure that these new labels are used consistently across the project and that they fully align with the Infracost tagging policies.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 695cdb3 and d951699.

Files selected for processing (1)

• .coderabbit.yaml (1 hunks)

Additional comments: 5

.coderabbit.yaml (5)

• 6-6: Enabling early access features can provide access to the latest functionalities but might also introduce instability or bugs. Ensure that the benefits outweigh the potential risks for your project.
• 8-8: The request_changes_workflow option being set to true ensures that changes are requested during reviews, which can enhance code quality by enforcing a review process. This is a good practice for maintaining high standards.
• 10-10: Enabling auto review can significantly streamline the review process by automatically analyzing and providing feedback on code changes. However, it's important to periodically review its effectiveness and ensure it aligns with your project's standards.
• 11-11: Disabling the poem feature indicates a preference for a more traditional review format. This is a matter of project policy or personal preference and seems reasonable depending on the context.
• 13-13: Enabling auto-reply in the chat configuration can improve responsiveness for automated interactions. Ensure that the messages are configured to be helpful and informative to avoid confusion.