important-leather-2879607/10/2019, 8:53 PM
branch, we execute
as a sanity check before it is merged to
. Generally speaking, our gcloud credentials are provided via env
. Is there a recent pulumi update that could be causing:
I haven’t any idea why a gcloud config would be called here in our ci.
error: Get <https://220.127.116.11/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.
$ gcloud auth login
locally and have no env vars set and I can preview fine….more confused.
gcloud auth revoke
important-leather-2879607/10/2019, 10:39 PM
cli at all, I am creating service account credentials in an
stack, then supplying them system-wide with the env
. This has been working fine but a pulumi? update within the past three weeks has perhaps changed something.
important-leather-2879607/10/2019, 11:57 PM
important-leather-2879607/11/2019, 1:38 AM
. Is there a way to have the cli report a stack trace to the console?
you are using?
You can get very verbose logs with
which might help here?
pulumi preview --logtostderr -v=9 --debug 2> out.txt
important-leather-2879607/11/2019, 1:46 AM
did I run
, 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.
gcloud auth activate-service-account