restatedev / restatedev/journal-encryption
Standardize format such that Restate Server can recognize encrypted data
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We ultimately want a way for Restate Server to be able to reject all non-encrypted data, to let users configure client-side encryption as a strict requirement.
To achieve that, we first need a way for Restate Server to be able to identify whether an invocation body or journal contents is actually encrypted.
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
The issue names no files, tests, or entry points. Start by identifying where invocation bodies and journal contents are formatted and parsed, then determine how Restate Server can reliably distinguish encrypted from non-encrypted data. Done means a standardized format exists that allows the server to identify whether each payload is encrypted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100