Add feature to concurrently update/delete AWS API Gateway method settings #13497
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the error encountered while updating/deleting
aws_api_gateway_method_settings
resources concurrently. Right now we get the following error if parallelism is > 1 and we try to update/delete > 1 method_settingsThis issue was highlighted in a comment - #483 (comment) - which suggested using daisy chaining to resolve it. But when using
for_each
we cannot use daisy chaining as per this discussion - https://discuss.hashicorp.com/t/is-there-a-way-to-daisy-chain-depends-on-for-resources-created-using-count-or-for-each/8467There is no other workaround except for using parallelism value 1 which slows down the entire deployment as API Gateway is just one part of many resources created/updated.
Community Note
Relates #483
Release note for CHANGELOG:
Output from acceptance testing: