docker / docker/secrets-engine
Derive context to group secrets by project
Open
- Dominant language
- Go
- Stars
- 91
- Forks
- 16
- Avg merge
- 9h 3m
- Merged PRs (30d)
- 24
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
--globalflag available for anydocker mysecretsubcommand - if
--globalis set, no realm is appended/prefixed - if
--globalis not set (default), the outer git repo is used to namespace / realm-prefix all set/list/delete/get operations - if
--globalis not set and there's no outer git repo, the CLI errors
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.
Assessment
This issue has not been assessed yet.