You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Confirmed in 3.9.0 as well. This problem extends to the .sops.yaml config as well. We set an aws_profile there in our KMS key_groups and it gets ignored, but if we use AWS_PROFILE=test sops then it works as expected.
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
The text was updated successfully, but these errors were encountered: