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

seems this issue is related?
<https://github.com/terraform-providers/terraform-provider-google/issues/5898>

i saw that github issue the other day and used `autogenerate_revision_name` to solve the 409

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?

I opened this issue:
<https://github.com/pulumi/pulumi-gcp/issues/338>

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