Feature Request: Add --secrets value= for specifying secret directly on CLI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
Secrets that I need to provide are present as exported environment variables on the build server.
Rather than having to create files on the build server (and thus risk the secrets being left behind on the build server), I would like to specify the secret directly in the command line like:
docker build --no-cache --progress=plain --secret id=mysecret,value=${GITLAB_ENVIRONMENT_VARIABLE} .
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
Start at the Docker CLI build command and reproduce the documented --secret invocation from the issue. Trace how the existing secret options are parsed and passed onward, then verify that a value supplied directly on the command line is accepted without requiring a file. The issue does not name specific source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100