Fix variable typo

[brettcurtis]

Summary by CodeRabbit

• Chores
  • Updated variable names for Datadog integration to enhance consistency.
• Documentation
  • Added default and resource-specific usage values for various Google Cloud resources in the Datadog module documentation.
• Chores
  • Updated Terraform provider version for improved compatibility.
• Chores
  • Removed environment-specific configurations from the infracost file.
• Documentation
  • Updated Terraform provider version in the regional infrastructure documentation.

[coderabbitai]

Walkthrough

The recent updates involve renaming variables for consistency in the Datadog integration within the infrastructure configuration files. Additionally, adjustments were made to the Google provider version in both global and regional configurations to align with the latest version. In the Infracost configuration, default and resource-specific usage values for Google Cloud resources were added to enhance cost estimation within the Datadog module.

Changes

File(s)	Change Summary
global/infra/README.md, .../main.tf, .../variables.tf, .../.terraform.lock.hcl	Renamed Datadog integration variables for consistency and updated Google provider version.
global/infra/infracost/production.yml	Added usage values for Google Cloud resources in the module.datadog[0] module.
infracost.yml	Removed environment configurations.
regional/infra/README.md	Updated Google provider version.

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

Commits

Files that changed from the base of the PR and between 2583534 and 997aac9.

Files selected for processing (4)

• global/infra/README.md (1 hunks)
• global/infra/infracost/production.yml (1 hunks)
• global/infra/main.tf (1 hunks)
• global/infra/variables.tf (1 hunks)

Additional comments: 7

global/infra/variables.tf (2)

• 27-27: The variable enable_datadog has been correctly renamed for consistency and clarity. This change aligns with best practices for naming boolean variables with an action-oriented prefix, enhancing readability.
• 33-33: The variable enable_datadog_cloud_cost_management has been correctly renamed, improving the clarity and consistency of the variable naming convention. This change is in line with best practices for boolean variable naming, making the codebase more maintainable.

global/infra/main.tf (2)

• 34-34: The count attribute for the Datadog module has been correctly updated to use the renamed variable enable_datadog. This change ensures that the Datadog integration is conditionally deployed based on the updated variable, aligning with Terraform best practices for conditional resource creation.
• 38-38: The enable_cloud_cost_management attribute within the Datadog module has been correctly updated to reference the renamed variable enable_datadog_cloud_cost_management. This ensures that the cloud cost management feature of Datadog is correctly enabled based on the updated variable, maintaining consistency and clarity in the codebase.

global/infra/README.md (1)

• 31-32: The documentation in README.md has been correctly updated to reflect the renamed variables enable_datadog and enable_datadog_cloud_cost_management. This update ensures that the documentation remains accurate and consistent with the codebase, aiding in the clarity and usability for developers and users.

global/infra/infracost/production.yml (2)

• 9-20: The addition of default usage values for google_bigquery_dataset, google_pubsub_subscription, and google_pubsub_topic resource types in the production.yml file is a significant improvement. These default values provide a baseline for cost estimation, which is crucial for effective cloud cost management. It's important to ensure these values are periodically reviewed and updated based on actual usage patterns to maintain accuracy.
• 26-35: The inclusion of resource-specific usage values for instances within the module.datadog[0] module is a commendable effort to provide more precise cost estimations. This level of detail can significantly aid in managing cloud costs more effectively. However, it's essential to verify these values against actual usage to ensure they remain relevant and accurate over time.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 997aac9 and 70cef9a.

Files selected for processing (3)

• global/infra/.terraform.lock.hcl (1 hunks)
• infracost.yml (1 hunks)
• regional/infra/README.md (1 hunks)

Files skipped from review due to trivial changes (1)

• infracost.yml

Additional comments: 2

regional/infra/README.md (1)

• 12-12: The update of the Google provider version to 5.18.0 in the README documentation is noted. Ensure compatibility with the rest of the project and check for any required adjustments in the Terraform configurations due to this version change.

global/infra/.terraform.lock.hcl (1)

• 26-39: The update of the Google provider to version 5.18.0 in the .terraform.lock.hcl file, along with the associated hashes, is noted. Please ensure that these hashes are correct and verify the compatibility of this provider version with the project's Terraform configurations.