-
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 #37897
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Pre AWS SDK for Go v2 migration (v5.44.0):
|
Relates #37732. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.54.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. |
Terraform Core Version
1.5.5
AWS Provider Version
5.53.0
Affected Resource(s)
Expected Behavior
Multiple routes should be added to a single integration without error.
Actual Behavior
When creating multiple routes a conflicting error pops up.
Relevant Error/Panic Output Snippet
Error: creating API Gateway v2 Route: operation error ApiGatewayV2: CreateRoute, https response error StatusCode: 409, ConflictException: Unable to complete operation due to concurrent modification. Please try again later.
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
This issue was already fixed once (see #18018). I searched through the files and found that this fix was deleted with this Pull Request: #36490
The file that contained the fix changed during time. But the latest file containing it was on path: internal/service/apigatewayv2/service_package.go
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: