In Dispatch solo, we want to have eventing/subscription functionalities the same as previous Dispatch. Since Dispatch solo won't rely on K8s, the old event-driver as a k8s deployment will be changed to docker container.
Possible Implementation
Deploy event-driver as docker container
Maintain the same "Cron-style" event driver
Filtering based on source type and event type
Complexity
[ ] Low - Simple enhancement or bug fix, no architectural changes or refactoring
[ ] Medium - Change requires some thought, but is relatively isolated
[ ] High - Significant architectural change or large refactor
Feature Request
Detailed Description
In Dispatch solo, we want to have eventing/subscription functionalities the same as previous Dispatch. Since Dispatch solo won't rely on K8s, the old event-driver as a k8s deployment will be changed to docker container.
Possible Implementation
Complexity