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
feat(aws-lambda): improvements to the code and runtime APIs (#945)
* Simplify usage of assets for Lambda code. Instead of `Code.directory` and `Code.file`, just use `Code.asset(path)` and we will determine if this is a directory.
* If `Code.asset` (or the deprecated `Code.file`) references a non-zip file, an error will be thrown.
* Simplify `lambda.Runtime` by deleting the interfaces `InlinableRuntime` and `InlinableJavaScriptRuntime`, which fixes#902 and fixes#188
* Remove `lambda.InlineJavaScriptLambda`.
* Remove `lambda.Runtime.NodeJS43Edge` which fixes#947
* Add inlining support for NodeJS 8.10 (fixes#947)
* No need to provide read permissions for asset (fixes#664)
BREAKING CHANGE: The construct `lambda.InlineJavaScriptLambda` is no longer supported. Use `lambda.Code.inline` instead; `lambda.Runtime.NodeJS43Edge` runtime is removed. CloudFront docs [stipulate](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-requirements-limits.html#lambda-requirements-lambda-function-configuration) that you should use node6.10 or node8.10. It is always possible to use any value by instantiating a `lambda.Runtime` object.
0 commit comments