fix: ctrlc doesn't do cluster-name env detection

[dacbd]

Summary by CodeRabbit

• Chores

  • Helm chart version updated to 0.1.4

• New Features

  • Added cluster name parameter to sync service configuration for multi-cluster deployments

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The ctrlc-sync Helm chart receives a version bump from 0.1.3 to 0.1.4, and the CronJob template is updated to pass a --cluster-name flag to the sync command's container arguments.

Changes

Cohort / File(s)	Summary
Chart Version Bump charts/ctrlc-sync/Chart.yaml	Helm chart version incremented from 0.1.3 to 0.1.4.
CronJob Configuration charts/ctrlc-sync/templates/cronjob.yaml	Added --cluster-name=... flag to container command arguments for the sync operation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• fix(ctrlc-sync): missing provider #28: Modifies the same cronjob.yaml file by extending container command-line arguments, suggesting coordinated chart updates.

Suggested reviewers

• jsbroks
• adityachoudhari26
• zacharyblasczyk

Poem

🐰 A version bump, a flag so new,
The cluster name now finds its cue,
In charts we hop, from 0.1.3,
To 0.1.4, sync flows free! 🎉

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dacbd/cli-name-arg

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}