Refine gcluster deploy flag checks to only consider local flags.#5372
Conversation
gcluster deploy
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 resolves a bug in the 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 addresses a bug where global flags were incorrectly rejected when using gcluster deploy with a deployment directory. The change from createCmd.Flag() to createCmd.LocalFlags().Lookup() correctly distinguishes between flags local to the create command and global persistent flags. This ensures that only flags specific to creation are disallowed, while global flags are permitted. The fix is correct and well-targeted.
gcluster deploy|
/gcbrun |
|
@Neelabh94 could you please approve? |
dd5375a
into
GoogleCloudPlatform:develop
Submission Checklist
Running
gcluster deploy <DEPLOYMENT> --download-dependenciesfails. This change fixes this so we are supporting global flags for that command.