sops command doesn't read --aws-profile flag value
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
version: sops 3.8.0
Problem: The problem is noticed if you have multiple AWS profiles and you want to specify which credentials to use while using the sops command, unfortunately, sops keeps using the default profile from your ~/.aws/credentials
Workaround: export the aws profile of interest to the ENV var AWS_PROFILE
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 sops command entry point and trace how the --aws-profile flag value is parsed and passed to AWS credential selection. Reproduce the issue with multiple profiles, then verify that the flag selects the requested profile instead of the default or AWS_PROFILE fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100