-
Notifications
You must be signed in to change notification settings - Fork 1k
Group Cluster Failover flags into a single command flagSet #6905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Group Cluster Failover flags into a single command flagSet #6905
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary of ChangesHello @XiShanYongYe-Chang, 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 focuses on a cleanup effort by refactoring the configuration options related to cluster failover. The primary goal is to enhance code clarity and maintainability by renaming the relevant struct and file, and by organizing its command-line flags into a distinct group. This change ensures that the configuration for cluster failover is explicitly named and presented, making it easier for developers and users to understand and manage. 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. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request effectively groups the cluster failover flags into a dedicated flagSet, which improves the clarity of the command-line interface. The related options and configurations have been consistently renamed from FailoverOptions to ClusterFailoverOptions across the codebase. The changes are well-contained and correctly implemented. I've added a few minor suggestions to further improve the code by removing magic strings and updating a comment.
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6905 +/- ##
==========================================
- Coverage 46.39% 46.39% -0.01%
==========================================
Files 697 697
Lines 47764 47766 +2
==========================================
- Hits 22162 22161 -1
- Misses 23932 23936 +4
+ Partials 1670 1669 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: changzhen <[email protected]>
795dca6 to
1589cb3
Compare
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request effectively refactors the cluster failover flags into a dedicated flagSet, which improves the clarity and organization of the command-line interface. The changes are well-executed, including renaming FailoverOptions to ClusterFailoverOptions for better specificity and replacing magic strings with constants from policyv1alpha1, which enhances maintainability. Overall, this is a great cleanup that sets a good template for grouping other parameters in the future. I have one suggestion to improve the validation logic for the new options.
|
/retest |
|
/cc @RainbowMango |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Currently, there are an increasing number of parameters in the generic component of karmada-controller-manager. It might be a good idea to group these parameters according to the functions or controllers they handle.
Let's first take Cluster Failover as an example to create a template, and then we will gradually group and process other parameters in the following sections.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: