monkut
monkut
@souravjamwal77 Sorry, the initial step wasn't to bring the `kappa` source code into zappa, but rather *wrap* it's usage so that `kappa` could be refactored out eventually.
@aalmazan @Andrew-Chen-Wang Noticed this Vulnerability, any known actions on this? https://osv.dev/vulnerability/GHSA-5vcc-86wm-547q
Interesting idea. However, supporting view/editing via the AWS console is not a priority at the moment.
Not sure if we really want to allow creation of a default zappa_settings.json when one isn't present for commands that expect/require it. To allow this action, the user should show...
Try running `zappa unschedule STAGE` with the setting in your `zappa_settings.json` then remove it from the `zappa_settings.json` after it gets unscheduled.
Is there an ImportError occurring? I what way is it, not uploaded correctly?