Repository navigation
[platform] Prevent installed packages deletion - #2273
Conversation
Signed-off-by: Myasnikov Daniil <[email protected]>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a change to prevent the automatic deletion of installed packages when they are no longer enabled or explicitly disabled. By applying the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Helm helper template now adds a Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Code Review
This pull request adds the helm.sh/resource-policy: keep annotation to the metadata section of Package kind resources within the _helpers.tpl file, specifically to two different Package templates. A review comment suggests refactoring the duplicated Package resource definition into a separate helper template to improve maintainability and reduce redundancy across these templates.
| annotations: | ||
| helm.sh/resource-policy: keep |
There was a problem hiding this comment.
The annotations block, including helm.sh/resource-policy: keep, is duplicated across the cozystack.platform.package and cozystack.platform.package.optional templates. To improve maintainability and reduce redundancy, consider extracting the common Package resource definition (up to spec.variant) into a separate helper template. This would allow both cozystack.platform.package and cozystack.platform.package.optional to include this common base, ensuring consistency and simplifying future modifications.
|
Successfully created backport PR for |
|
Successfully created backport PR for |
What this PR does
Adds annotation
helm.sh/resource-policy: keepto all packages to prevent its automatic deletion when:1, Package added to
disabledPackagesparameter incozystack.cozystack-platformpackage2. Package removed form
enabledPackagesparameter incozystack.cozystack-platformpackageThis change bring back docs explained behavior - platform administrator should manually delete package if needed.
Release note
Summary by CodeRabbit