Should `set`/`--set` takes it value from a file rather than a command line parameter?
Open
Nobody has claimed this yet.
area/CLI
enhancement
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
At least as an option, in order to avoid a sensitive value from being leaked in the process list?
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
Review the CLI handling for set/--set and determine how an optional file-based value could be accepted. Check how command-line values currently reach the secret-setting path, then define completion as supporting file input without exposing the sensitive value in the process list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100