feat(apigateway): validate integrationHttpMethod with non-MOCK integration types#28316
Conversation
tmokmss
left a comment
There was a problem hiding this comment.
Thanks @lpizzinidev!
I was worried about possibility of breaking the current behavior, but it seems it's safe to add this validation according to the CFn doc.
IntegrationHttpMethod
Specifies the integration's HTTP method type. For the Type property, if you specify MOCK, this property is optional. For Lambda integrations, you must set the integration method to POST. For all other types, you must specify this property.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Pull request has been modified.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
integrationHttpMethodmust be specified for non-MOCK integration types.This PR adds validation to prevent build-time errors.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license