You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If API Gateway is generated from openapi, an integration is required for every method. Currently the error message from AWS is "No integration defined for method (Service: ApiGateway, Status Code: 400, Request ID: xxx), which is not helpful.
For now, at least some kind of validation should happen when generating the integrations. A good-to-have optional feature would be to generate a mock-integration for missing integrations.
The text was updated successfully, but these errors were encountered:
Maybe we could actually extend the mock integration concept and have a defaultIntegration prop where one could assign any kind of supported integration that would be assigned to paths without any integration?
This would tackle 2 different use cases:
During development one could setup a mock integration for non-implemented methods while building the API setup
If all API methods is handled by let's say external HTTP(S) endpoint or a Lambda proxy, then defining only one defaultIntegration would handle everything without having to explicitly define all paths and methods in CDK
If API Gateway is generated from openapi, an integration is required for every method. Currently the error message from AWS is
"No integration defined for method (Service: ApiGateway, Status Code: 400, Request ID: xxx)
, which is not helpful.For now, at least some kind of validation should happen when generating the integrations. A good-to-have optional feature would be to generate a mock-integration for missing integrations.
The text was updated successfully, but these errors were encountered: