lowRISC / lowRISC/opentitan-provisioning

Create ProxyBuffer RPC methods to check if payloads have been processed by the registry

Open
#175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
16
Forks
13
Avg merge
2d 3h
Merged PRs (30d)
18

Description

ProxyBuffer exposes two methods for registering devices: `RegisterDevice` and `BatchRegisterDevice`. Internally, these register the device(s) in an internal SQLite database. Additionally, the service has an async process (syncer) that periodically reads the local database to find unregistered records, send them to an external registry, and mark them as registered.

However, we don't have a way of figuring out which records have already been processed in the registry besides manually querying the internal database (which might not be an easy thing to do depending on the SQLite config).

We should have additional RPC methods in ProxyBuffer to check this status: something like `CheckDeviceStatus` and `BatchCheckDeviceStatus`.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading ProxyBuffer's RegisterDevice and BatchRegisterDevice methods, then trace the syncer and its internal SQLite records to understand how registry processing is recorded. Define the individual and batch status responses and add RPCs that report whether each payload has been processed by the external registry.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sqlite
Domain
api, backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.