support `--kms`, `--aws-profile` options when decryption
Open
Nobody has claimed this yet.
area/keyservice
keyservice/awskms
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
I think that options should be passed when decryption like
sops --kms ${KMS_ARN} --aws-profile ${AWS_PROFILE} -d encrypted.json > decrypted.json
But, this proposal may be not appropriate to this project. Do you think about it?
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 from the decryption command path exercised by sops --kms ${KMS_ARN} --aws-profile ${AWS_PROFILE} -d encrypted.json. Check how these options are currently handled during decryption and verify the command with an encrypted JSON file. Done means both options are accepted and used for the requested decryption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cli, cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100