My idea behind that was :
-
each topic have it specific JSON payload -> each topic needs to be handled differently
-
(because above) - the routing on endpoint that would consume webhook (for…
I had an idea to 'cache' interesting and non-interesing topics for each webhook after filer funciton is ran ... but did not have time to play with it for now.
At first I was thinking this way. But after going over few use-cases I ened it like this way. My justification:
- topic are organised in
category.subcategory.etc - when looking for specific…
Yes, but my low golang skill was not able to reproduce. And I found this way much simple to do and understand.
Updated. Using middleware/router way
- configuration moved closer to user-defined topics:
# Webhook configuration
webhooks:
- events : [ '*' ]
# URL for webhook
url:…
I didn't try that. Mostly cause I'm not (yet) familiar w/ Watermill :) Sound like better idea (less code)
#1181 is based on "only" notification - and the PR there is doing http call in sync way (in the code handling notification).
I tried to follow the pattern of event-driven actions (how for…