Derive context to group secrets by project

Open
#194 0 comments 0 reactions 1 assignee View on GitHub

@joe0BAB is already working on this.

Since Aug 6, 2025.

  • #196 by @joe0BAB — closed without merging

Assessment

This issue has not been assessed yet.

Description

The realm system allows to group secrets for organizing and avoiding name clashes.

Terminology: realm == namespace

Examples:

Let's say you have two projects (git repos), and in each there needs to be a secret named foo. Then these options exists:

my-project/foo
my-project/bar
vs
my-other-project/foo
vs
foo
vs
root/foo

Also the pattern matching logic build in the secrets engine allows to then filter all secrets per project, e.g., my-project/* only gives all secrets of project my-project.

Thus, we suggest the following CLI ux:

  • there's a --global flag available for any docker mysecret subcommand
  • if --global is set, no realm is appended/prefixed
  • if --global is not set (default), the outer git repo is used to namespace / realm-prefix all set/list/delete/get operations
  • if --global is not set and there's no outer git repo, the CLI errors
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.