monkut

@liuwenjie Currently the linter is failing due to too complex. `get_event_source()` needs to be refactored. Looks like the easiest way to resolve this issue is to move the \*EventSources outside...

@NinitoAS Not sure why this got closed... I'm looking at getting the next release out in Novemenber. Can you fix the conflicts here, so we can get this merged in?

As I understand `kappa` is pretty defunct, so if this is currently supported by kappa (last release Feb 14, 2017) we'll need quite a bit of work to migrate from...

Here's the related code where zappa schedules events: https://github.com/zappa/Zappa/blob/master/zappa/core.py#L2775 zappa uses [kappa](https://github.com/garnaat/kappa) to update the s3 event source. I suspect the unschedule `remove()` action may be removing the notification configuration....

The easiest workaround we could implement in zappa is to provide a flag to ignore redeploying events. In your case, I would use zappa for packaging and separate deployment. I'd...

zappa stores it's source code in the defined bucket. Currently zappa will not deploy without an s3 bucket.

Assume this is related to asynchronous task execution. PRs are welcome. Will close if no activity on this issue by end of 2022.

Yes, it looks like the intention is to update the PATH_INFO in environ, but the updated value is not applied.

Yes, if you can that would be great. I don't think we have testcases in place for this so I'd like to get it covered. What is your path and...

Yes, I believe that the infrastructure stage created by zappa in the API Gateway will include the stage name as well, so this needs to be included here. Is there...