apigw-data-validation-tf: Update AWS provider and remove duplicate body validation resource #2802
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.
Issue #, if available:
Description of changes:
While trying to deploy the
apigw-data-validation-tf
sample, I've noticed that the Lambda Runtime has been updated to Python 3.13, but the Terraform AWS provider has been pinned to the4.x
version. Python 3.13 is not a valid value for this older runtime, and this makes Terraform reject and fail. I've updated it to5.x
.It also did not deploy because the
Model
resource was declared both in the OpenAPI body of the REST API as well as its own Terraform resource, leading to an exception:So I've deleted the OpenAPI body to make sure the
Model
was declared in Terraform and could be accessed in theaws_api_gateway_method
.The sample now deploys correctly against AWS.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.