Automatically create integration webhooks when missing [RUN AS-IF-FOSS]
What does this MR do?
Previously we were silently failing if the webhook could not be saved when the integration was edited, which led to further exceptions later when the integration was trying to execute the webhook.
The webhook is really only used to associate records in web_hook_logs
,
so we can create it automatically when needed and don't have to
backfill existing integrations.
We now also raise errors if the webhook cannot be saved, which should help us diagnose why this is failing in the first place.
Addresses #335218 (closed), and would make #335685 (closed) redundant.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are 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. -
This change is backwards compatible across updates, or this does not apply.
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.) - [-] I have tested this MR in all supported browsers, or it's not needed.
- [-] I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Related to #335218 (closed)
Edited by Markus Koller