This PR addresses eliminates the API Gateway Stage issue by replacing the API Gateway (which only ever defined a single resource anyway) with a Lambda Function URL. It also splits the deployment package into separate SAM templates – one for standalone (lambda-only) and another for the CloudFront/caching/6MB workaround-enabled version.
Specific changes:
Replace API Gateway with Lambda Function URL (Fixes #63)
Refactor SAM templates into standalone and cloudfront (Fixes #56 #58)
Update documentation to reflect standalone/cloudfront split
Remove yarn.lock in favor of package-lock.json and update docs to use npm instead of yarn
I haven't been able to publish this version to the Serverless Application Repository yet because of aws/serverless-application-model/#2421, but I'll keep watch on that issue and update when I can.
This PR addresses eliminates the API Gateway Stage issue by replacing the API Gateway (which only ever defined a single resource anyway) with a Lambda Function URL. It also splits the deployment package into separate SAM templates – one for standalone (lambda-only) and another for the CloudFront/caching/6MB workaround-enabled version.
Specific changes:
yarn.lockin favor ofpackage-lock.jsonand update docs to usenpminstead ofyarnI haven't been able to publish this version to the Serverless Application Repository yet because of aws/serverless-application-model/#2421, but I'll keep watch on that issue and update when I can.