Argument order for --decrypt
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
It took me a while to figure this out, but should argument order matter here? 🤔
$ sops -d secrets.yaml
envSecrets:
deploy-key: 12345
$ sops -d secrets.yaml --extract '["envSecrets"]["deploy-key"]'
envSecrets:
deploy-key: 12345
$ sops -d --extract '["envSecrets"]["deploy-key"]' secrets.yaml
12345
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 by tracing the CLI handling for -d, --extract, and the input filename, then reproduce both command orders shown in the issue. Determine the intended consistent behavior for argument order and verify the result with tests covering these commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100