Only package project code into lambda, place all other dependencies in lambda layer

[suzikuo]

Only package project code into lambda, place all other dependencies in lambda layer
Because the lambda code is too large, I am unable to view it through the AWS console, and it is reasonable to place dependencies in the lambda layer for small projects

[monkut]

Interesting idea.
However, supporting view/editing via the AWS console is not a priority at the moment.

[github-actions]

Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.

[joelwebb]

I was doing some local testing with this just to speed up our CI/CD pipelines when deploying. If there is a way in zappa to disable to downloading/packaging the dependencies on zappa deploy dev with a potential flag ( --no-deps ) this could be an alternative to using zappa to deploy, creating the lambda layer & adding the layer to zappa config settings.

To disable the pip installs on deploy when you already have a cached dependencies in the lambda layers, it would cut our CI/CD from 2.5 minutes to <30s since ~90% of our time is spent waiting for zappa to reinstall the packages on every deploy eventhough we cache the local venv and have dependencies cached on AWS.