-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Gateway v2 integration & route: ConflictException due to concurrent modification #18018
Comments
@dovydas-phrasee Thanks for raising this issue. |
@ewbankkit Around 30 |
I get no errors creating 30 integrations in parallel for a single API:
@dovydas-phrasee You could try lowering the parallelism value for |
@ewbankkit tried to lower parallelism to 5, but it didn't help. And got error for creating
But the error is not consistent |
There is a similar restriction with AppSync APIs (#16211). I am interested in contributing to a solution here. I believe the provider could implement a per-api-id semaphore to prevent concurrent access. This solution seems novel in the codebase, so I would like maintainer feedback about the best approach 🙏 |
I am experiencing a similar issue when trying to create
It appears a similar issue was fixed for apigatewayv1 by adding retry logic here: terraform-provider-aws/aws/config.go Lines 679 to 686 in 5e6e4df
Could we potentially add that same fix for apigatewayv2? |
I'm also seeing this, with I think the v1 fix mentioned in the previous comment is related to the nearly identical issue #16439. |
@bflad 👋 i've been trying to get my head around under which PR the work mentioned in #16439 (comment) was done? Looking in the changelog it looks like there is no PR
Been hit by this issue last few days and would love to see if it can be fixed even in a simple way of extending the same code against v2 |
@maryelizbeth 👋 sorry to tag you directly, by a long shot is anything you or anyone in your team can help getting this issue back on the radar ? Nowadays a lot of folks are using either v1 or v2 of the API GW and i'm very much surprised that up until now this issue hasn't been a priority. Would appreciate if the priority gets bumped (i'm not there yet to contribute , otherwise i would have done it ... already spent 2 weeks fighting with this issue) |
Seeing the same error when trying to create a simple serverless function with a custom authorizer. This is a bad bug. Resource handler returned |
Hey guys, any ETA about this fix? |
Also an issue for private service integrations :/ Please give ETA for the fix? |
The same issue with aws_apigatewayv2_api_mapping. To deal with the issue I have to execute terraform apply with -parallelism=1 which drastically increases execution time |
hello! any news about the ETA for fixing this? Still happens with |
Hi guys, I am also getting
This should be fixed... |
I think the related commit that was implemented for API Gateway v1 (and REST API) is this one d906813 I'm not familiar with AWS Go SDK internals nor Terraform handlers but would it be possible to use something very similar for API Gateway v2 by importing
it seems the apigatewayv2 package in AWS Go SDK implements the exact same Exception |
This functionality has been released in v4.59.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Getting error when creating multiple
aws_apigatewayv2_integration
andaws_apigatewayv2_route
resourcesCommunity Note
Terraform CLI and Terraform AWS Provider Version
Terraform v0.13.6
AWS provider 3.24.0
Affected Resource(s)
Terraform Configuration Files
The text was updated successfully, but these errors were encountered: