monkut

I believe I've installed from a private github repository before, this is refering to a private package repository, right?

I've experienced this as well, where I've built out a project with testing and development packages which resulted in a package too big for lambda. Resulting in me re-creating the...

marking as duplicate of: https://github.com/zappa/Zappa/issues/677

I'm going to close this as it's an old migrated issue. If you are running zappa from within the associated venv, I don't think this should be a problem.

(currently running this branch in a personal project of mine to confirm stability)

no response closing.

the `concurrent` package is included in `exclude` by default. You can assign`exclude: []` to resolve this issue. There is a PR open that will clarify the documentation regarding `exclude`. https://github.com/zappa/Zappa/issues/1191#issuecomment-1316484748

I have questions about how effective the keep_warm function is, however, this issue is only about changing the existing keep_warm value from the current 4 minutes to a more appropriate...

This looks like a package build issue. I assume most build on their systems and deploy to aws, where it appears that on packaging the wrong version will be picked/installed....

@elip-OE Can you add a testcase confirming that the given cli value is properly changed and doesn't exceed the max configurable ephemeral_storage value? (throws proper error