kubesec doesn't show any errors when there is no default 'gcloud auth application-default login'

[ShyykoSerhiy]

Connected issue #14

[shyiko]

@ShyykoSerhiy any chance you can attach sample output here?
60b9dc7 has an implication that user is now required to have access to all the keys (not just one of them) to get to the DEK. This needs to be fixed. Having the output of kubesec with and without --debug would really help here.

[toshitanian]

Same here. It took several hours to find that I need to run gcloud auth application-default login to decrypt the secret.
kubesec decrypt xxx.yaml --debug just said that the file can't be decrypted.

Attempting to decrypt DEK with GCP KMS key projects/xxxx/locations/global/keyRings/xxx/cryptoKeys/xxx
Unable to decrypt Data Encryption Key (DEK)

[silviogutierrez]

@toshitanian : GOOGLE_APPLICATION_CREDENTIALS worked for me.

However, I mostly use the gcloud cli, so I'm used to using CLOUDSDK_AUTH_CREDENTIAL_FILE_OVERRIDE. I kept running into your issue.

Since kubesec uses an sdk, it won't actually respect CLOUDSDK_AUTH_CREDENTIAL_FILE_OVERRIDE. Setting GOOGLE_APPLICATION_CREDENTIALS worked.