chore: add description variable for chart

[RoseSecurity]

what

• The description variable is declared but unused. This addition allows users to set a description for the Helm release

Summary by CodeRabbit

• New Features
  • Added support for specifying a description when deploying Helm releases.

[coderabbitai]

Walkthrough

A new attribute, description, was added to the helm_release resource block in the Terraform configuration. This attribute references the var.description variable. No other changes or modifications to resource logic or flow were introduced.

Changes

File(s)	Change Summary
src/main.tf	Added description attribute to helm_release resource, assigned from var.description.

Poem

A line of code, a note to say,
The helm release has words today!
Description added, clear and neat,
With Terraform, our work’s complete.
🐇✨

---

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/main.tf (1)

21-21: Good addition—consider default/null-handling and docs update

Adding the description field wires the previously unused variable into the helm_release, making the chart configurable as intended. Two small follow-ups you may want to tackle:

1. If var.description can be null or empty, some Helm provider versions will still send an empty string and mark the release as “changed” on every plan/apply. Guarding with try(var.description, null) or setting a sane default ("") in variables.tf avoids that noise.
2. Remember to expose the variable in the module/README inputs table so consumers see the new capability.

Nothing blocking—code is correct.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f5d7b8d and e7d3a2f.

📒 Files selected for processing (1)

• src/main.tf (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

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

[RoseSecurity]

/terratest

[goruha]

@RoseSecurity is it ready to merge?

[RoseSecurity]

@goruha Good to go. Nothing crazy with this one

[github-actions]

These changes were released in v1.538.0.