when deploying with zappa command, some of Python packages are replaced with equivalent lambda compiled packages which is good in some situation. But often they are outdated and there is no option given to disable this behavior. Also when using lambdaci/python docker image as base for CI/CD this step is not necessary. The lambda-packages is big and kind of bloated.
Possible Fix
there should be a command to zappa package and zappa deploy or some settings config to disable replacing lambda packages.
Instead of giving lambda-packages as dependency, we can keep a PyPI mirror with wheels which can be used by pip when installing/deploying.
Steps to Reproduce
pip install pusher pyopenssl
zappa deploy (the cryptography 2.2.1 is replaced by ~1.9) which results in error.
Context
when deploying with zappa command, some of Python packages are replaced with equivalent lambda compiled packages which is good in some situation. But often they are outdated and there is no option given to disable this behavior. Also when using
lambdaci/python
docker image as base for CI/CD this step is not necessary. The lambda-packages is big and kind of bloated.Possible Fix
zappa package
andzappa deploy
or some settings config to disable replacing lambda packages.pip
when installing/deploying.Steps to Reproduce
Your Environment