discussion: webhooks

[c-nv-s]

I liked your pgstream project and this one as well. it reminded me of https://github.com/tableflowhq/db-webhooks

Might be cool to have a TUI webhook manager. Just a suggestion.

[mujib77]

Thanks for the suggestion and the reference!
A TUI webhook manager is an interesting idea
being able to manage and monitor database webhooks directly from the terminal would fit well with Cosmo's philosophy.

I'll keep this in mind for a future version.
Feel free to elaborate if you have specific
features in mind.

[c-nv-s]

no specific feature request, but I suppose the idea is to create a TUI version of db-webhooks, a user could, for example, set up a listener for DELETE events from a Postgres table/s and then send the contents of the deleted row as the payload along with custom headers to a defined url.
You could store the info for each webhook in a separate Table/DB in Postgres, or use a separate sqlite3 database for separation or if permissions might be an issue.

[mujib77]

That's a clear use case essentially pgstream
(my WAL reader) already captures DELETE events with the full row data. Adding a webhook delivery layer on top would make it a complete pipeline.

I'll consider this for a future version of either
pgstream or cosmo. Thanks for explaining!