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
Google API clients have the ability to use credentials from a well-known path. This path is where the gcloud SDK writes them when you execute gcloud auth login --update-adc or gcloud auth application-default login. There is no need to set the GOOGLE_APPLICATION_CREDENTIALS envvar in this case (though you can to override the path). And from the code side, there is no client config needed for it to automatically use that credential. It Just Works(R).
PR #953 broke app default credentials while making the GCP KMS integration more CI-friendly. If one did NOT set GOOGLE_CREDENTIALS, sops would try to create the KMS client with a zero-byte JSON credentials slice, which caused a JSON parse error.
Only a small change is necessary to let #953 coexist with GOOGLE_APPLICATION_DEFAULT credentials. PR incoming.
The text was updated successfully, but these errors were encountered:
I am running into the same issue (viaduct-ai/kustomize-sops#178) and would like to push this issue once more.
Is there any reason why your related PR does not get merged? Although there are work-arounds for this, I strongly believe that this bug should get fixed as per the expectations one has in how to setup the client environment variables.
Google API clients have the ability to use credentials from a well-known path. This path is where the
gcloud
SDK writes them when you executegcloud auth login --update-adc
orgcloud auth application-default login
. There is no need to set theGOOGLE_APPLICATION_CREDENTIALS
envvar in this case (though you can to override the path). And from the code side, there is no client config needed for it to automatically use that credential. It Just Works(R).PR #953 broke app default credentials while making the GCP KMS integration more CI-friendly. If one did NOT set
GOOGLE_CREDENTIALS
, sops would try to create the KMS client with a zero-byte JSON credentials slice, which caused a JSON parse error.Only a small change is necessary to let #953 coexist with
GOOGLE_APPLICATION_DEFAULT
credentials. PR incoming.The text was updated successfully, but these errors were encountered: