oxidecomputer / oxidecomputer/steno
`SecStore` has no read methods
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 170
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Hello 👋 While implementing a SecStore for our own persistence layer I noticed that there's no way to for a SecClient to read from a SecStore, it can only write to it. This means that it's up to the clients to implement crash recovery for their app. This seems like ideal to be implemented by the SecClient instead, which would require additional methods to SecStore to be able to read from the SecStore.
Is this something that you'd be interested in adding to steno?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the SecStore and SecClient definitions and reviewing how SecClient currently writes to SecStore. Define the read and crash-recovery behavior from the existing persistence flow; done means SecClient can recover persisted state through SecStore without requiring each client to implement recovery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100