RFC: Webhooks for Tuist Events

[marekfort]

@pepicrft

Or at least store them, and we can build this UI in a follow-up.

I agree we should store them, and the UI can be added in a follow-up.

@pepicrft

When building an integration with webhooks, it’s very convenient to forward them to a locally running instance of your server, so I was thinking we could make this convenient for users through the CLI. Otherwise, they have to bring an additional tunnel, which adds unnecessary friction in the process of building on us.

That’s a good idea We can and should do that.

@pepicrft

How would you model this from the Elixir side? Were you thinking about creating an Oban worker per event, and then letting Oban run those? If so, I was thinking whether it’d make sense to do some batching, not for the use case you mention above, but to make efficient use of the HTTP connections. For example, if we receive 100 events going to the same URL in a short period of time, we could warm a Finch pool of connections and schedule some of them for the same pool. We can also treat this as a future optimization.

Yes, I planned to use Oban workers. I think some batching might be useful, I’ll take that into account during the implementation and will see if, initially, we would just limit the worker concurrency and let those events wait in the Oban queue or if it would make sense to outright batch them.