You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an app I work on we create SQS queues as part of deployment and, as a result, we don't know their ARNs before deploying the application. This makes it tricky to put those ARNs in our zappa_settings.yaml.
I propose a default_event_handler where users can set the path to a function to be called for any events which are not handled using the event handlers. This would provide an escape hatch for users like us, as well as a way for early adopters of new AWS technologies to use aws events that zappa doesn't explicitly support yet.
The text was updated successfully, but these errors were encountered:
jiaaro
changed the title
There is no way to configure SQS event handlers dynamically
There is no way to configure SQS (or any) event handlers dynamically
Jun 9, 2020
jiaaro
changed the title
There is no way to configure SQS (or any) event handlers dynamically
There is no way to configure SQS event handlers dynamically
Jun 9, 2020
In an app I work on we create SQS queues as part of deployment and, as a result, we don't know their ARNs before deploying the application. This makes it tricky to put those ARNs in our
zappa_settings.yaml
.I propose a
default_event_handler
where users can set the path to a function to be called for any events which are not handled using the event handlers. This would provide an escape hatch for users like us, as well as a way for early adopters of new AWS technologies to use aws events that zappa doesn't explicitly support yet.I have begun implementing this in my fork
The text was updated successfully, but these errors were encountered: