Observable stream for changing secrets

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
security

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.

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.

Dominant language
Go
Stars
91
Forks
16
Avg merge
9h 3m
Merged PRs (30d)
24

Contributor guide

No contributing guide indexed for this repository

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.

More from docker/secrets-engine

All issues in docker/secrets-engine

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.