Move webhook post-send writes to their own service
What does this MR do?
This MR addresses #331919 (closed) by:
- moving the webhook writes to a separate service
- arranging for this service to be run in a new worker
This enables the web-hook service itself to be marked as read-only, and run on a replica, but have the writes be queued for application to master.
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
Related to #331919 (closed)
Edited by Alex Kalderimis