Page MenuHomePhabricator

[backup-service] implement endpoint to upload User Keys
ClosedPublic

Authored by kamil on Nov 5 2024, 9:05 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 22, 8:30 AM
Unknown Object (File)
Sat, Apr 19, 12:33 PM
Unknown Object (File)
Sat, Apr 19, 9:39 AM
Unknown Object (File)
Sat, Apr 19, 4:30 AM
Unknown Object (File)
Sat, Apr 19, 4:09 AM
Unknown Object (File)
Fri, Apr 18, 1:36 AM
Unknown Object (File)
Wed, Apr 9, 6:13 PM
Unknown Object (File)
Wed, Apr 9, 11:57 AM
Subscribers

Details

Summary

Part of ENG-6145.

Tracked in ENG-9672.

image.png (818×2 px, 211 KB)

Depends on D13875

Test Plan

Tested in D13879

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Nov 6 2024, 3:41 AM
kamil edited the summary of this revision. (Show Details)
kamil added inline comments.
services/backup/src/http/handlers/backup.rs
111–122

We need an old backup item to add new holder to user data

124–158

this could probably implemented better but not sure - curious for reviewers perspective

bartek added inline comments.
services/backup/src/http/handlers/backup.rs
124–158

From data safety and consistency perspective, this code makes a lot of sense - we make sure each backup has its own attachment holders. It's slightly worse about performance due to multiple Blob service calls, however this code won't be run frequently.
A potential improvement would be to use the batch-holder endpoints, but this is a follow-up for a separate diff, it can be deferred.

This revision is now accepted and ready to land.Nov 6 2024, 6:12 AM
services/backup/src/http/handlers/backup.rs
124–158

Good call, created ENG-9874