important-leather-28796
07/10/2019, 8:53 PMdevelop
branch, we execute pulumi preview
as a sanity check before it is merged to master
. Generally speaking, our gcloud credentials are provided via env GOOGLE_CLOUD_KEYFILE_JSON
. Is there a recent pulumi update that could be causing:
error: Get <https://35.226.191.153/openapi/v2?timeout=32s>: error executing access token command "gcloud config config-helper --format=json": err=exit status 1 output= stderr=ERROR: (gcloud.config.config-helper) You do not currently have an active account selected.
Please run:
$ gcloud auth login
I haven’t any idea why a gcloud config would be called here in our ci.gcloud auth revoke
locally and have no env vars set and I can preview fine….more confused.chilly-crayon-57653
important-leather-28796
07/10/2019, 10:39 PMgcloud
cli at all, I am creating service account credentials in an identity
stack, then supplying them system-wide with the env GOOGLE_CLOUD_KEYFILE_JSON
. This has been working fine but a pulumi? update within the past three weeks has perhaps changed something.chilly-crayon-57653
important-leather-28796
07/10/2019, 11:57 PMwhite-balloon-205
important-leather-28796
07/11/2019, 1:38 AMpulumi preview
. Is there a way to have the cli report a stack trace to the console?white-balloon-205
kubeconfig
you are using?
You can get very verbose logs with pulumi preview --logtostderr -v=9 --debug 2> out.txt
which might help here?important-leather-28796
07/11/2019, 1:46 AMprovider_plugin.go:514] Provider[kubernetes, 0xc00308ab40].Diff(
now thinks I have no gcloud account. Which repo has that code?pulumi update
did I run gcloud auth activate-service-account
, it appears now that I need it to preview as well.
So, not a problem, I just assume it has some better checking or validation.