Atlas App Services
2 results found
-
Allow manually disabled trigger to resume without resume token
I am filing a feature request for the option to: Disable a trigger manually and be able to restart it without using a resume token (i.e. such that DB events that occurred while it was disabled will be ignored by the trigger, and it will simply start listening for new events upon restart).
8 votes -
Triggers on DB level rather than single collections only
Change streams support events on DB level or single collections, but triggers are limited to single collections. Which means that if we wanted to listen on changes in a generic way, we would have to setup a trigger for each collection and set them up with AWS EventBridge (and think about new triggers when new collections are generated).
Given that the underlying tech (change streams) supports DB-level subscriptions, we would really like to see that on the UI, too.
2 votes
- Don't see your idea?