so i m encountering the 409 from GCP that s mentioned here

Question

so i m encountering the 409 from GCP that s mentioned here <https pulumi community slack com archives CRFUR2DGB p1581516688055000> It seems like there wasn t any traction on this thread I remember once upon a time convincing `pulumi up` to generate ludicrously verbose logs that included the HTTP responses from GCP s REST API I might be able to bludgeon Cloud Run into submission if I can see the specific error that it returns with that 409 response Can anyone help

hallowed-rain-9096 · Answer

seems this issue is related <https github com terraform providers terraform provider google issues 5898>

clean-autumn-55516 · Answer

i saw that github issue the other day and used `autogenerate revision name` to solve the 409

hallowed-rain-9096 · Answer

i thought `autogenerate revision name` was supposed to fix the 409 according to that issue it didn t help me I had to destroy and rebuild my stack

hallowed-rain-9096 · Answer

It seems that `autogenerate revision name` isn t a comprehensive solution for the 409 errors when deploying new Cloud Run revisions I m still having these issues I m going to experiment with adding a random string to the revision name Are there any Pulumi folks that could weigh in on this please

hallowed-rain-9096 · Answer

I opened this issue <https github com pulumi pulumi gcp issues 338>

hallowed-rain-9096 · Answer

Okay I m still getting this issue with cloud run giving me a 409 error on subsequent deploys weary