-
Notifications
You must be signed in to change notification settings - Fork 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
chore(apigatewayv2): move lambda and http proxy integrations to the 'integrations' module #11339
Conversation
…integrations' module We now have a `@aws-cdk/aws-apigatewayv2-integrations` module that is intended to hold all integration of HTTP APIs with other services. In line with this, move `LambdaProxyIntegration` and `HttpProxyIntegration` classes to this module. BREAKING CHANGES: `LambdaProxyIntegration` and `HttpProxyIntegration` classes have moved to the `@aws-cdk/aws-apigatewayv2-integration` module.
I was about to implement it :D |
Haha. Sorry, I wasn't aware. |
Thank you for contributing! Your pull request will be updated from master 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 master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
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