Design: backup resource status (rollup) for PartiallyFailed backups - #273
Joeavaikath wants to merge 1 commit into
Conversation
Documents post-backup rollup CLI approach using existing DownloadRequest metadata paths, for OADP-8697 / issues migtools#269-271. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Joeavaikath The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks 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 |
Why the changes were made
High-level design for oadp-cli work under #269 (OADP-8697): after a backup finishes
PartiallyFailed, expose per-logical-unit status (e.g. per-VM) by rolling up existing Velero metadata.Adds
docs/design/backup_resource_status-design.mdcovering:ProcessDownloadRequest, non-admin describe fetching resource-list / results / volumeinfo / itemoperations, plus Backup CR + tarball ownerRefs)resource-status/vm-status)Design only — no implementation.
How to test the changes made
docs/design/backup_resource_status-design.mdfor accuracy and scopeMade with Cursor