chore: add managedBy terraform tag to all resources

[hussedev]

Summary by CodeRabbit

• Chores
  • AWS resources are now automatically assigned standardized metadata tags, ensuring consistent tracking and improved resource management across all deployment environments.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update several Terraform configuration files across different deployment environments by adding a new default_tags block within the AWS provider configuration. This block introduces a tags map containing two key-value pairs: ManagedBy set to "Terraform" and AppName set to "Indexer". These modifications ensure that resources created by Terraform are automatically tagged with the specified metadata. No changes were made to the declarations of exported or public entities in any of the files, and existing configuration details, such as the AWS region settings, remain unchanged.

---

📜 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 0cc7124 and d24de3b.

📒 Files selected for processing (4)

• deployment/environments/production/main.tf (1 hunks)
• deployment/environments/staging/main.tf (1 hunks)
• deployment/registry/main.tf (1 hunks)
• deployment/state/main.tf (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (4)

• deployment/registry/main.tf
• deployment/environments/staging/main.tf
• deployment/state/main.tf
• deployment/environments/production/main.tf

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

• GitHub Check: e2e-tests / E2E Tests

---

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

deployment/registry/main.tf (1)

3-8: Enhanced Tagging with default_tags Block

The new default_tags block correctly introduces the required tags (ManagedBy = "Terraform" and AppName = "Indexer"). This update will help with consistent resource identification across your deployment.

deployment/environments/staging/main.tf (1)

13-20: Default Tags Block with Minor Formatting Inconsistency

The tagging block is properly implemented, providing the expected ManagedBy and AppName tags. However, note that the indentation for the AppName key is slightly misaligned compared to ManagedBy. Consider adjusting the whitespace for improved readability and consistency across files.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 37ebd66 and 0cc7124.

📒 Files selected for processing (4)

• deployment/environments/production/main.tf (1 hunks)
• deployment/environments/staging/main.tf (1 hunks)
• deployment/registry/main.tf (1 hunks)
• deployment/state/main.tf (1 hunks)

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

• GitHub Check: test / Unit and Integration Tests

🔇 Additional comments (2)

deployment/environments/production/main.tf (1)

13-18: Consistent Default Tags Configuration

The default_tags block is added correctly within the AWS provider. It mirrors the tagging strategy from other environments, ensuring that resources are uniformly tagged.

deployment/state/main.tf (1)

1-9: Correct Default Tags Configuration in State Management

The addition of the default_tags block in the provider configuration is accurate and consistent with the other environment files. This ensures that AWS resources managed through state storage are properly tagged for easier management and tracking.