No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

The error doesn’t happen when using `gcloud` command line tool

Yes, a bunch of people hit this earlier, you may find it with search, but I guess the solution was to use a service account

That would seem to be the obvious solution but I’ve had no luck with it (`gcloud auth activate-service-account`)

I’m having no trouble creating a cloud function using `gcloud` itself

Ok, it looks like it’s not enough to use `gcloud auth activate-service-account` but instead, `export GOOGLE_CREDENTIALS=$(cat key.json`  for Pulumi to use SA credentials

<@UB39JFCKC> worth updating your blog post to mention this?

<@UB3BGTV63> this one <https://www.pulumi.com/blog/simple-serverless-programming-with-google-cloud-functions-and-pulumi/> ?

Ahh - I misread this as being about Cloud Run - I though I recalled folks hitting the same error for that API.  But if this is just a broad issue - perhaps we should instead update core Pulumi GCP docs to more strongly encourage service accounts?

I actually don’t know how widespread it is… but I _think_ I only saw messages about the Cloud Functions in this Slack.

Again I don’t know, I’ve always used service accounts