Repository navigation
Backup rework pt 2 - #1967
Backup rework pt 2#1967Timofei Larkin (lllamnyp) merged 2 commits into
Conversation
Signed-off-by: Andrey Kolkov <[email protected]>
Signed-off-by: Andrey Kolkov <[email protected]>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the
✨ Finishing touches🧪 Generate unit tests (beta)
Important Action Needed: IP Allowlist UpdateIf your organization protects your Git platform with IP whitelisting, please add the new CodeRabbit IP address to your allowlist:
Failure to add the new IP will result in interrupted reviews. 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 |
Summary of ChangesHello Andrey Kolkov (@androndo), 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 significantly enhances the backup capabilities by introducing a dedicated 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. Changelog
Activity
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. 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.
Code Review
This pull request refactors the backup functionality by introducing BackupClass to simplify the Plan and BackupJob APIs. The dashboard changes align with this simplification. My review includes a correction for a potentially critical bug in the Velero backup strategy template and a couple of suggestions to improve the user interface for creating backup plans.
| labelSelector: | ||
| apps.cozystack.io/application.Kind: {{ .kind }} |
There was a problem hiding this comment.
The labelSelector field appears to be structured incorrectly. According to the Velero API specification, it should contain a matchLabels field. The current structure may not be parsed correctly by Velero, which could cause backups to fail to select any resources.
labelSelector:
matchLabels:
apps.cozystack.io/application.Kind: {{ .kind }}| createFormItem("spec.applicationRef.kind", "Application Kind", "text"), | ||
| createFormItem("spec.applicationRef.name", "Application Name", "text"), |
| "clusterNameVar": "clusterName", | ||
| }, | ||
| }), | ||
| createFormItem("spec.schedule.type", "Schedule Type", "text"), |
There was a problem hiding this comment.
The Schedule Type is based on the PlanScheduleType enum. Using a select input type instead of text would be more appropriate and prevent users from entering invalid values.
| createFormItem("spec.schedule.type", "Schedule Type", "text"), | |
| createFormItem("spec.schedule.type", "Schedule Type", "select"), |
| snapshotMoveData: true | ||
|
|
||
| ttl: 720h0m0s | ||
| itemOperationTimeout: 24h0m0s |
There was a problem hiding this comment.
The itemOperationTimeout is set to 24 hours, which is significantly longer than Velero's default of 1 hour. Such a long timeout could cause the entire backup process to hang for an extended period if a single item operation gets stuck. Consider reducing this to a more reasonable value (e.g., 4h0m0s) to prevent potential stalls in the backup queue.
itemOperationTimeout: 4h0m0s3eaadfc
into
feat/backup-work-consolidation
What this PR does
Release note