04/12/2022, 7:55 PM
Hello, I'm trying to troubleshotting a stack update. Every time when I run
pulumi update
the process want to update my resource (db-instance) on my gcp even when diff operations shows that everything are the same. When I use
pulumi update --diff --json > diff-file.json
I can see the newState and oldState for resource is exactly the same but pulumi still want to update it with error like this:
... 1 error occurred:
        * Error, failed to update instance settings for : googleapi: Error 412: Condition does not match., staleData
Could anyone advice me how I could track it down?


04/13/2022, 3:34 PM
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>&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: (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 🙂


04/13/2022, 6:28 PM
thank you for the answer, I managed to move forward with it using
pulumi refresh
after that next pulumi update started work for me
🙌 1