Initial Webhook Implementation - #3099

The PR tracks an initial implementation for outbound webhooks. This will adhere-to/include the following:

• Webhooks will be managed by those that can manage application settings (Generally admin users).
• They will take a name and endpoint to configure.
• You can select any system event (As shown in audit log) or choose to send all events.
• Webhooks will be POST requests with fixed-format JSON.
  • An event property will detail the event that was trigged.
  • A text property will be set where possible to provide a human readable description of the event for potential direct slack (Or slack compatible) usage.
• No custom permission handling will be considered for this implementation.

TODO

• Finish admin management UI.
• Build event call logic.
• Add example of format to the admin management UI.
• Add ability to deactivate/activate in the management UI.
• Mention availability of webhooks in the API docs page.
• Define strategy for queue based calling (Optional).
• Testing
  • Permissions
  • Calling
  • Management Interface

Queue Strategy

Defaults to sync. Can use an async queue via QUEUE_CONNECTION=sync. Will then need a queue worker via:

php artisan queue:work --sleep=3 --tries=3 --max-time=3600

Ideally will need that ran via systemd or similar, with php artisan queue:restart ran upon update.

Docs Todo

• Create new "Notifications & Webhooks" page.
• Detail changes needed to use database queue where performance is desired.
  • Include a systemd setup steps for a default script-installed Ubuntu setup.