Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Deploying new revisions of Cloud Run resources yields 409: Conflict
See original GitHub issueDeploying new revisions of Cloud Run resources is failing due to the GCP API giving an error response of 409: Conflict. This occurs whether or not the AutoGenerateRevisionName field is set (as mentioned by this Terraform provider issue: https://github.com/terraform-providers/terraform-provider-google/issues/5898). I’ve tried AutoGenerateRevisionName and manually generating a random name as well.
Issue Analytics
- State:
- Created 3 years ago
- Comments:27 (6 by maintainers)
Top Results From Across the Web
Managing Revisions | Cloud Run Documentation
The following considerations apply to revisions: You can specify whether a new revision receives all, none, or some of the traffic, you can...
Read more >How To Fix the “409 Conflict” Error (5 Methods) - Kinsta
1. Check the Requested URL ... As we mentioned earlier, the “409 Conflict” error can arise from incorrect information in a PUT request....
Read more >Migrating a Cloud Run deployment from shell to Terraform
When Terraform returns an Error 409: Resource already exists , it means that Terraform's local state doesn't match the project state. We can...
Read more >API Docs - GitLab Docs
409 Conflict, A conflicting resource already exists. ... GitLab also returns the following additional pagination headers: ...
Read more >Pipelines to deploy on azurePortal suddenly broken with 409
we set a pipeline to publish a AppService on Azure Cloud, we have been using it for more than a year and this...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Doing a refresh worked once, but when I added
pulumi refresh --yesto my CD script prior topulumi up --yesit failed again with a 409, so I think there’s something else at play here as well. Are there any considerations I should weigh (other than it takes longer to refresh then deploy) when addingpulumi refresh --yesto my CD scripts?Yes, if you don’t want to clean it, can you please DM to me on slack.pulumi.com? Alternative, lee@ via email works, too.