serverless-layers icon indicating copy to clipboard operation
serverless-layers copied to clipboard

Serverless.js plugin implementing AWS Lambda Layers, reducing lambda size, warm-up, and deployment time.

Results 48 serverless-layers issues
Sort by recently updated
recently updated
newest added

Serverless is able to generate its own deployment bucket and this plugin should be able to read from it when not explicitly specified by users.

Hi, would like to have this feature so users can specify number of layer versions to keep. This feature is needed to avoid old layer versions to take up much...

enhancement
next-release

Hi, after setup my layers pointing to a bucket I'm getting this warning: ``` Serverless: [ LayersPlugin ]: => default ... ○ Uploading layer package... ... ○ OK... ... ○...

## Issue Just dropping this down somewhere to note / for people with this problem. Not sure if it's a bug or expected behaviour. I tried to introduce `serverless-layers` to...

help wanted
investigating

When i redeploy my lambda it uses the layer version 1 even though i the latest version is 2 after changing the package.json i changed it manually and it works...

I'm implementing a CI on top of my app and one of the steps I want to run is `sls package` just to make sure all the configurations are there...

Using serverless-layers 2.5.3 when sls deployed, the all layers using same packages resulting `AWS Error: Function code combined with layers exceeds the maximum allowed size of 262144000 bytes` like #51...

investigating

This is a feature request to support deleting previous layer versions when a new version is deployed Same feature as option "retain" in core serverless https://www.serverless.com/framework/docs/providers/aws/guide/layers/

enhancement
help wanted
next-release

Hello, This is more of a question. I am not able to find a way to define name of layer. If we can define name of layer then, it will...

If no deployment bucket is configured, `sls deploy` will create a bucket dynamically, but this plugin does not pick up that bucket name and instead fails the entire deploy. This...