Remove an http target's max_queue_size (closes #477)

Nothing in delivery ever read it, so setting it bounded nothing. The field, the "Max Queue Size" line in the target list, its README row and the tests that set or checked it are gone. An existing database keeps its old column, which is no longer read. Model: opus-5-5
2026-10-02 23:23:58 +00:00
parent 3489d6909a
commit 48176e6425
4 changed files with 3 additions and 16 deletions
@@ -1699,7 +1699,6 @@ events should be forwarded.
 | `active`         | boolean    | Whether deliveries are enabled (default: true) |
 | `config`         | JSON text  | Type-specific configuration |
 | `max_retries`    | integer    | Total delivery attempts for `http` and `slack` targets, not retries on top of the first: 0 is a single fire-and-forget attempt with no retries and no circuit breaker, and a value of N makes N attempts in all, with exponential backoff and a per-target circuit breaker. Ignored by `database` and `log` targets |
-| `max_queue_size` | integer    | Stored and shown on the target's detail view, but not enforced anywhere yet: nothing in the delivery engine consults it. Queue depth is set by the two fixed 10,000-entry channels |

 **Relations:** Belongs to Webhook. Has many Deliveries.