Per a 2016 blog post, Stemma supported triggering webhooks on various repository events a-la Github webhooks.
Do Stemma webhooks still exist? (per the Stemma API packages, they seem to)
If they do, what is the schema of the webhooks? And are there egress restrictions on which URLs Stemma can call?
Using the new custom endpoints feature, could a custom endpoint be registered as a Stemma webhook?
We would also be interested in this as we want to setup automated code review agents that would get triggered by opened PRs.
The Foundry platform uses the Stemma Webhooks APIs to trigger workflows such as running checks, which is why these appear in API definitions. This API remains supported and is still actively used.
However, as you’ve identified, there is currently no API or support for adding egresses, which makes these webhooks unsuitable for use outside the platform.
We’re aware of demand for federating code and triggering external actions, including webhooks, and we’re starting to plan improvements in this area. Stay tuned!
From talking with Alexandru Beloiu it sounds like egress might not be necessary for reaching out to the Foundry enrollment’s front door, and specifically to a custom action. If that’s the case, all that’s necessary to start using webhooks are the schema of the payload that Stemma sends, and a bit more information on the register-webhook API (specifically about the shared secret: are there any requirements on what this is).
We are also interested in leveraging a similar approach.