-
Notifications
You must be signed in to change notification settings - Fork 93
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(snapshots): GetBackup details endpoint should support new dr #5058
feat(snapshots): GetBackup details endpoint should support new dr #5058
Conversation
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.
LGTM, left a suggestion/question
pkg/handlers/backup.go
Outdated
Success bool `json:"success"` | ||
Error string `json:"error,omitempty"` | ||
BackupDetails []snapshottypes.BackupDetail `json:"backupDetails"` | ||
Deprecated_BackupDetail *snapshottypes.BackupDetail `json:"backupDetail"` |
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.
I wonder if this is better VS changing where we use this in the UI?
backupInfo: result.backupDetail, const snapshotDetails = response.backupDetail;
Else, should we have a store to clean this up once the UI is updated?
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.
Is something like this correct?
result.backupDetails && result.backupDetails.length > 0 ? result.backupDetails[0] : null
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.
Or this?
result.backupDetails?.[0]
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.
updated
What this PR does / why we need it:
Adds support to backup details endpoint for new DR.
Which issue(s) this PR fixes:
Does this PR require a test?
Does this PR require a release note?
Does this PR require documentation?