New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#2275] Allow for multiple webhooks and event filtering #2286
Conversation
pathType: Prefix | ||
backend: | ||
service: | ||
name: api-communication | ||
port: | ||
number: 80 | ||
- path: /conversations.info |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ljupcovangelski and @pascal-airy I simplified this file a lot by using prefix matching. We don't have to specify every single route if e.g. all /conversations*
routes go to api-communication
.
|
||
onEvent = (body: string) => { | ||
const json = JSON.parse(body) as EventPayload; | ||
switch (json.type) { | ||
case 'channel': | ||
case 'channel.updated': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AudreyKj and @thorstenairy The websocket event names will change a bit in the next release.
resolves #2275
TODO:
X-Airy-Content-Signature
headerUpgrade procedure:
/webhooks.info
1.1 Call
/webhooks.info
and note downurl
andheaders
1.2 At
9.
call the/webhooks.subscribe
with this dataIf there is no existing webhook, steps 2. - 4. can be skipped. If there is no pre-existing webhook deployment at all, then only the admin app needs to be reset.