Feature request: filter and/or edit format for outgoing webhooks

[morgenstern]

Hi Pulumi team,

we love the new webhooks feature and use it to post updates to our Slack tech channel. But we also have use the renovate bot for automated dependency updates of our code. This results in very spammy notifications for every (automated) deployment without being able to visually differentiate them from our dev team deployments in Slack as information about the source (like the git branch that was merged) is missing.

How you could help us?

• make it possible to filter webhook triggers not only by certain events but introduce an advanced filter system that let's users filter webhook triggers by any of the deployments metadata
• make it possible to change the content / body of the outgoing webhook. This way users could eg. built their own notification design using JSON / Slack Block Kit and inject data from the Pulumi deployment.

Thanks for your good work!

Greetings Helge

[EvanBoyle]

@morgenstern thanks for the suggestion. In the meantime, standing up a lambda or webserver to process webhooks and implement custom transformations is always an option. Here is an example that stands up a webhook processor that forwards events to slack: https://github.com/pulumi/examples/tree/master/aws-ts-pulumi-webhooks

[morgenstern]

Thanks for your feedback and the link @EvanBoyle. We currently solve this with https://pipedream.com/ but a native solution without workaround would be even smoother.