Modify the kubectl-apply manifest helm_release_naming#5438
Conversation
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 refactors the naming convention for Helm releases within the kubectl-apply module. By moving away from random hex suffixes in favor of deterministic names derived from manifest metadata, the changes improve predictability and maintainability of deployed resources. Additionally, the integration of a module-level identifier ensures better tracking and configuration management. Highlights
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-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
|
There was a problem hiding this comment.
Code Review
This pull request updates the kubectl-apply module to use more descriptive Helm release names based on manifest names or source filenames, and introduces the injection of module_id. Feedback indicates that the new naming logic lacks sanitization for DNS compliance (e.g., handling underscores), which is required for Helm releases. Additionally, the apply_manifests variable definition must be updated to include the name attribute for the new logic to function. Finally, removing the random suffix from release names may lead to naming collisions and leaves unused resources and outdated documentation that should be addressed.
2a5df87 to
1ca1c25
Compare
|
SUCCESS: |
5c5b740 to
15a2df9
Compare
35394df to
4f44093
Compare
b381af3 to
66c3b69
Compare
038146a
into
GoogleCloudPlatform:develop
This reverts commit 038146a.
…eCloudPlatform#5438)" This reverts commit 343c79f.
This PR modifies the
kubectl-applymanifest Helm release naming to improve resource naming clarity, uniqueness, and stability:nameattribute if defined in the manifest object schema..yaml,.yml, and.tftplfrom auto-derived names.${var.module_id}-rawcombined with a deterministic hash for raw content, ensuring uniqueness without requiringrandom_idresources.This approach provides flexible, deterministic naming while maintaining clarity and avoiding resource conflicts. The
README.mdhas been updated accordingly.Submission Checklist
NOTE: Community submissions can take up to 2 weeks to be reviewed.
Please take the following actions before submitting this pull request.