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
CDK support for HTTP API Gateways is currently alpha
The new Lambda Function URL support is currently all that is used
Removing deploy of API Gateway now would speed up deploys
To-Do
Make API Gateway optional in all CDK constructs
Allow the API Gateway Origin to be missing on the CloudFront distribution
Use S3 as the default Origin on CloudFront
Add support to change the S3 Origin to a Custom Origin (Lambda etc) - [ ] Move MicroAppsAPIGwy into it's own CDK Construct - [ ] Remove API Gateway as an option from the MicroApps CDK Construct - [ ] Remove the API Gateway npm modules for CDK from the microapps-cdk package - [ ] Do not publish the API Gateway CDK Construct for now - [ ] Publish the updated MicroApps construct
Items moved to #293 for moving the support into a new module in next minor version.
The text was updated successfully, but these errors were encountered:
* Make API Gateway optional - default skip
Fixes#291
* Point to S3 origin when no APIgwy origin
* Only add execute-api permission when needed
* Override the S3 origin
* Only upload CDK synth zip when labeled
Saves about two minutes in deploy job
* Try caching installed node modules
* Make more module installs optional
* Fix CDK construct optional install
* Attempt to fix SigV4 failure
* Add OriginShield
* fix path
* Fix module cache for jsii
* Fix createNextDataPathRoute
* Fix app URLs listed on PR
* Fix link
Motivations
To-Do
- [ ] MoveMicroAppsAPIGwy
into it's own CDK Construct- [ ] Remove API Gateway as an option from theMicroApps
CDK Construct- [ ] Remove the API Gateway npm modules for CDK from the microapps-cdk package- [ ] Do not publish the API Gateway CDK Construct for now- [ ] Publish the updated MicroApps constructItems moved to #293 for moving the support into a new module in next minor version.
The text was updated successfully, but these errors were encountered: