Webhook to API

[bjendres]

Similar to #18 and #26, we want to proxy to be able to receive webhooks/callbacks and forward the configuration to the target system's API.

For that, this hook needs the following features:

• multiple configurations, one default
• IP/Range filter
• parameter sources (POST/json, ...)
• parameter sanitation
• response processing (mapping of API response to HTTP status codes)

[pbatroff]

This is implemented and works well with correct configuration setup.

In here and here return values from the internal CiviAPI is exposed.

I would propose to return 200 here and log the error internally to civiproxy_log, since the webhook got parsed and forwarded to the API correctly.

@bjendres do you have an opinion here?

This was already implemented, since the civi http code isn't returned, but 200 is always returned

[pbatroff]

I think we can close here