docker / docker/secrets-engine
Dynamic Scopes
@joe0BAB is already working on this.
Since Dec 10, 2025.
- Dominant language
- Go
- Stars
- 91
- Forks
- 16
- Avg merge
- 9h 3m
- Merged PRs (30d)
- 24
Description
Consider a store with following sample content:
proj1/foo
proj2/foo
foo
Possible generic scoping rules we could impose:
Prefix scoping: docker/mcp/** -> **
docker/mcp/foo
docker/mcp/proj1/foo
docker/mcp/proj2/foo
Wrap scoping:
docker/*/mcp/* -> */*
docker/foo/mcp (not a match)
docker/proj1/mcp/foo
docker/proj2/mcp/foo
docker/**/mcp -> **
Queries:
docker/proj1/foo/mcp -> proj1/foo
docker/foo/mcp -> foo
docker/**/mcp/* -> **/*
Queries:
docker/proj1/foo/mcp/day1 -> proj1/foo/day1
docker/mcp/day1 -> day1
docker/*/mcp/** -> */**
docker/**/mcp/** -> **/** -> ** -> illegal scoping rule
docker/*/**/mcp/**/* -> */**/**/* -> */**/* -> illegal scoping rule
docker/*/**/mcp/*/** -> */**/*/** -> */*/** -> illegal scoping rule
Scoping algorithm:
- must be a valid pattern
- compute the forwarded pattern
- verify if the forwarded pattern does not have any redundancy
- If redundancy: ambiguous scoping rule -> error
- If no redundancy: unique scoping rule -> pass
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.