Purge Outgoing Webhooks events and deliveries data

bullet_train-outgoing_webhooks/app/jobs/webhooks/outgoing/purge_job.rb

@@ -0,0 +1,14 @@
+class Webhooks::Outgoing::PurgeJob < ApplicationJob
+  queue_as :default
+
+  def perform(days_old = 90)
+    # Delete children first, then parents.
+    purge(Webhooks::Outgoing::DeliveryAttempt, days_old)
+    purge(Webhooks::Outgoing::Delivery, days_old)
+    purge(Webhooks::Outgoing::Event, days_old)
+  end
+
+  def purge(model, days_old)
+    model.where("created_at < ?", days_old.days.ago).delete_all
+  end
+end

bullet_train/docs/webhooks/outgoing.md

@@ -27,6 +27,8 @@ payment.generate_webhook(:succeeded)
 ## Delivery
 Webhooks are delivered asyncronously in a background job by default. If the resulting HTTP request results in a status code other than those in the 2XX series, it will be considered a failed attempt and delivery will be reattempted a number of times.
 
+All of the delivery attempts and events are stored in the database. There is a background job to purge records in these tables as they can grow large in size over time. You can schedule this job to purge records older than 90 days by default.
+
 ## Future Plans
  - Allow users to filter webhooks to be generated by a given parent model. For example, they should be able to subscribe to `post.created`, but only for `Post` objects created within a certain `Project`.
  - Integrate [Hammerstone Refine](https://hammerstone.dev) to allow even greater configurability for filtering webhooks.