restatedev / restatedev/journal-encryption
Separate encryption / decryption code from caching and request auth
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the code ties AWS KMS and caching together.
We should separate these, to make it easier to use other key management providers.
In particular, once we add request auth and auth-aware caching, this should be orthogonal to the actual kms and decryption logic.
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 code that currently combines AWS KMS, caching, and request authentication, then trace how these concerns share interfaces and call paths. Done means encryption and decryption can be used independently of caching and request authentication, leaving room for other key-management providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- backend-api-design, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100