chore(apigatewayv2): move lambda and http proxy integrations to the 'integrations' module #11339
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.
We now have a
@aws-cdk/aws-apigatewayv2-integrations
module that isintended to hold all integration of HTTP APIs with other services.
In line with this, move
LambdaProxyIntegration
andHttpProxyIntegration
classes to this module.BREAKING CHANGE:
LambdaProxyIntegration
andHttpProxyIntegration
classes have moved to the
@aws-cdk/aws-apigatewayv2-integration
module.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license