Method integration validation

[alma-cdk]

Method integration validation

[aripalo]

Agreed.

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