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 `project` value should also be picked up ambiently from any of the following ENV vars:

```
"GOOGLE_PROJECT",
"GOOGLE_CLOUD_PROJECT",
"GCLOUD_PROJECT",
"CLOUDSDK_CORE_PROJECT",
```

Honestly not sure why Google has decided not to pick this up directly from `gcloud config` as well - but it seems to be an intentional choice by Google engineers working on the Google Terraform Provider.

Regarding the error - this is the same as reported here: <https://github.com/pulumi/examples/issues/150>.

I have tried many times to reproduce that myself, but have been unable to.  I feel reasonably sure that some combination of the credentials and projects being used must not be correct (and GCP error messages here are unfortunately not too helpful), but would love to get to the bottom of this.  I can't figure out any way Pulumi could be related to these errors - but it's certainly possible.

If you have any more details you can share on specific user/role/project configuration you are using - could you add it to the issue linked above?

hey <@UB3BGTV63> thanks for your answer. I’m a bit disappointed by what you are reporting about the choices Google engineers made, but that’s making it clear, it seems I don’t have a choice here.

Thanks for the link to the issue, I will follow up anything I can get on this one in it. Indeed that shouldn’t be a pulumi specific, I’ll let you know if I find something