Page MenuHomePhabricator

[services][backup] CreateBackup 2/3 - handle non-data inputs
ClosedPublic

Authored by bartek on Jan 9 2023, 4:03 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, May 6, 11:55 PM
Unknown Object (File)
Wed, May 1, 11:32 PM
Unknown Object (File)
Apr 2 2024, 12:45 AM
Unknown Object (File)
Apr 2 2024, 12:45 AM
Unknown Object (File)
Apr 2 2024, 12:45 AM
Unknown Object (File)
Apr 2 2024, 12:44 AM
Unknown Object (File)
Apr 2 2024, 12:44 AM
Unknown Object (File)
Apr 2 2024, 12:44 AM
Subscribers

Details

Summary

This diff adds logic for processing non-data inputs (handler non-data-mode). After all of them are provided,
backup ID is generated and the put client is initialized and handler switches to "data mode", which is implemented in child diff.

Depends on D6197

Test Plan

The service builds and starts. Logic of this diff can be tested altogether with the child diff - see the description there.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Jan 9 2023, 5:35 AM
tomek added inline comments.
services/backup/src/service/handlers/create_backup.rs
56 ↗(On Diff #20706)

Should we log user id?

142–143 ↗(On Diff #20706)

It seems like we can conclude that we're in data mode just by checking if blob_client is present. But maybe it will change in the future diffs.

This revision is now accepted and ready to land.Jan 11 2023, 9:38 PM
services/backup/src/service/handlers/create_backup.rs
56 ↗(On Diff #20706)

We shouldn't: https://phab.comm.dev/D6247#187227
I'll remove this

  • Rebase, changed is_data_mode boolean to enum
  • Removed logging user_id