Feature request: support glob in credHelpers option
Open
Nobody has claimed this yet.
area/authentication
area/distribution
kind/enhancement
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
If I want to use ECR, I need to add each ECR registry to credHelpers like:
{
"credHelpers": { "123456.abc.ecr.us-east-1.amazonaws.com": "ecr-login" }
}
A good default would be:
{
"credHelpers": { "ecr.*.amazonaws.com": "ecr-login" }
}
It will work directly, and will remove eventual conflict with others amazonaws.com domains.
GCR seems to be fine. They use gcr.io domain directly. Same for Azure, azurecr.io.
Contributor guide
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 Docker CLI configuration handling for credHelpers and its existing registry matching behavior. Define done as supporting the proposed ECR-style glob patterns without changing exact matches or causing conflicts with other amazonaws.com domains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100