Page MenuHomePhabricator

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

Authored by kamil on Tue, Nov 5, 9:05 AM.
Tags
None
Referenced Files
F3163709: D13876.id45615.diff
Wed, Nov 6, 3:24 PM
F3163708: D13876.id45611.diff
Wed, Nov 6, 3:24 PM
F3163700: D13876.id.diff
Wed, Nov 6, 3:24 PM
F3163684: D13876.diff
Wed, Nov 6, 3:23 PM
F3161167: image.png
Wed, Nov 6, 3:41 AM
Subscribers

Details

Reviewers
varun
bartek
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.Wed, Nov 6, 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.Wed, Nov 6, 6:12 AM