Currently the Webhook is integrated in SkoHub Vocabs. It spins up a web server listening to a build endpoint and if POST-requests get sent, it triggers a build of a new vocab with SkoHub-Vocabs.
It is sensible to separate these into two different components. SkoHub Vocabs on the one hand for building the vocabulary and the webhook and server part on the other hand to process builds with SkoHub Vocabs or add more functionality, e.g. reconciliation.
Following things have to be done:
[x] separate SkoHub Vocabs and Webhook by putting the webhook in a distinct repository
[x] remove dependencies of webhook from SkoHub Vocabs
Currently the Webhook is integrated in SkoHub Vocabs. It spins up a web server listening to a build endpoint and if POST-requests get sent, it triggers a build of a new vocab with SkoHub-Vocabs.
It is sensible to separate these into two different components. SkoHub Vocabs on the one hand for building the vocabulary and the webhook and server part on the other hand to process builds with SkoHub Vocabs or add more functionality, e.g. reconciliation.
Following things have to be done:
This separation will be the basis for the work on the reconiliation part.