Backup Content Access and Download #649
No reviewers
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
servala/servala-portal!649
Loading…
Reference in a new issue
No description provided.
Delete branch "backup-access"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds the design doc for backup content access and download, the follow-up to the backup visibility work (#544): not "did a backup happen?" but "give me the bytes".
What the spec proposes
Direct bucket access. Users get raw access to their backup data with their own external tools (restic, barman-cloud, aws/rclone); the portal helps by revealing the per-instance bucket credentials (plus the restic repository password where applicable) and rendering ready-made command blocks.
Main design points
unmanagedBucketinstances, legacy StackGres PostgreSQL, Garage/generic bucket backends. Portal-mediated exports and in-portal browsing were considered and dismissed (recorded in the doc).WIP: Raw Backup Accessto WIP: Backup Content Access and DownloadWIP: Backup Content Access and Downloadto Backup Content Access and Download5ea151b97d632fedaef5