search

aws / chalice

Python Serverless Microframework for AWS
Apache License 2.0
10.66k stars 1.01k forks source link

Preserve Custom Lambda Layers #1916

Open antonpirker opened 2 years ago

antonpirker commented 2 years ago

First of all: Chalice is amazing! Great Job!

Now the "issue":

I have a third party Lambda Layer that I add to all my Lambda functions. I have a Chalice project with automatic_layer: True so it is creating a Lambda Layer with shared code. After each chalice deploy I have to add my third party Lambda Layer again to all my Lambda functions. Could chalice deploy check for custom Lambda Layers that are not generated by Chalice and re-apply them after a new version was deployed?

This would be great!

devoredevelops commented 2 years ago

I am curious as well to know if this is possible. Much the same as others posting issues within this repo, I too desire integration NewRelic's Python agent and/or NR's Lambda layer for full APM support.

amrishparmar commented 3 weeks ago

We have a similar issue. Our particular use case is that we use Sentry's Lambda integration that makes it easy to instrument all of our Lambda's from one place, but every time we run a chalice deploy the layer that provides the instrumentation gets removed and has to be manually re-enabled.