docker / docker/secrets-engine
Observable stream for changing secrets
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 91
- Forks
- 16
- Avg merge
- 9h 3m
- Merged PRs (30d)
- 24
Description
In some cases a client needs to listen on any changes that might've happened to the secret value so that they can immediately request an updated value.
It might not be possible to check for changes in all circumstances, but we could at least start thinking about common use cases - such as secrets stored locally.
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 locating the secret-storage implementation and how locally stored secrets are read, then determine which changes can be observed reliably. Done should define and implement an observable update mechanism for supported secret changes, with tests covering the selected common cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100