https://pulumi.com logo
#google-cloud
Title
# google-cloud
h

hallowed-rain-9096

04/30/2020, 10:03 PM
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?
c

clean-autumn-55516

04/30/2020, 11:31 PM
i saw that github issue the other day and used
autogenerate_revision_name
to solve the 409
h

hallowed-rain-9096

05/01/2020, 1:01 PM
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.
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?
Okay, I'm still getting this issue with cloud run giving me a 409 error on subsequent deploys 😩