-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat: use opsrequst to achieve backup and restore #45
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #45 +/- ##
=======================================
Coverage 42.88% 42.88%
=======================================
Files 222 222
Lines 28333 28281 -52
=======================================
- Hits 12150 12129 -21
+ Misses 14689 14668 -21
+ Partials 1494 1484 -10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Does the output of the command |
I think user should only concern the result, such as the backup name and cluster name. They don't need know the process. |
resolve the conflicts |
is it necessary to use opsRequest for backup and restore? This step will add an additional opsRequest object |
7475ba5
to
960c3df
Compare
If backup and restore logic have changed, we don't need to change the code in kubeblock and kbcli meanwhile. |
Better to set a default TTL seconds for opsRequest, avoid the opsRequest remained. |
ok, I have set |
No description provided.