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

To get some diagnostic data, here's a short snippet that should get you what you need in this case:
```TF_LOG=TRACE pulumi up -v=11 --logtostderr 2&gt;&amp;1 | tee -a pulumi_log.txt```
The environment variable asks the classic provider to bubble up data. If you were running other providers that don't use the Terraform bridge, there's another flag to use on the troubleshooting page.

Regarding your specific question, I think you're running into this one: <https://github.com/hashicorp/terraform-provider-google/issues/7200> (the Pulumi classic GCP provider is built on the same bridge as the Terraform one, so the errors are often very similar). See if the fix suggested there helps :slightly_smiling_face:

thank you for the answer, I managed to move forward with it using
```pulumi refresh```
after that next pulumi update started work for me