Page MenuHomePhabricator

[identity] Refactor DDB transactions to accept signatures
ClosedPublic

Authored by bartek on May 6 2024, 3:19 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 21, 7:03 PM
Unknown Object (File)
Sat, Dec 21, 7:03 PM
Unknown Object (File)
Sat, Dec 21, 7:03 PM
Unknown Object (File)
Sat, Dec 21, 7:02 PM
Unknown Object (File)
Sat, Dec 21, 7:02 PM
Unknown Object (File)
Nov 17 2024, 2:51 AM
Unknown Object (File)
Nov 17 2024, 12:54 AM
Unknown Object (File)
Nov 17 2024, 12:46 AM
Subscribers

Details

Summary

Decided to refactor the closure return type in transact_update_devicelist().
The tuple is a bit ugly and could get even uglier when adding more stuff (device list signatures here). Introduced UpdateOperationInfo struct instead with a simple builder pattern. Included the signatures as well.

Depends on D11898

Test Plan

Device list unit and integration tests. Verified that signatures are stored in DDB when calling the update RPC

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable