Closed jaredhobbs closed 3 years ago
Turns out we hit the code storage limit for the region due to all the different versions (100% of 75.0 GB). I'm in the process of deleting old versions as part of our deploy cleanup scripts.
We just hit that today. Turns out there is a Zappa setting to set the number of versions to keep: https://github.com/Miserlou/Zappa/blame/master/README.md#L919
"num_retained_versions":null, // Indicates the number of old versions to retain for the lambda. If absent, keeps all the versions of the function.
there's actually a setting for it already: num_retained_versions
.
edit: whoops, didn't see your edit; was replying to the original comment 🙃
Context
Running latest zappa in python 3.8 context.
slim_handler
set totrue
.Expected Behavior
Lambda should update with new code
Actual Behavior
Lambda fails to update due to "Code storage limit exceeded" exception.
Zappa has been running great for almost a year now. It even update successfully multiple times earlier today. Then it stopped working. I'm using the slim handler and the code is only 60mb zipped so I don't know why this just started failing. Here's the output: