Repository navigation
Persist webhook subscriptions to database instead of in-memory #502
Description
What
Webhook subscriptions are stored in-memory in webhook.service.ts. They're lost on server restart and don't work with multiple replicas.
Why
Production deployments use multiple pods. In-memory subscriptions are randomly lost on pod restart and are invisible to other pods.
Scope
In scope: Create webhook_subscriptions table, migrate to PostgreSQL, add CRUD API
Out of scope: Webhook event history, delivery tracking
Acceptance Criteria
- Subscriptions stored in PostgreSQL
- Survive server restart
- Work across multiple replicas
- CRUD API for subscription management
Technical Context
backend/src/services/webhook.service.ts— in-memory storagebackend/src/controllers/webhook.controller.ts— controllerbackend/src/db/migrations/— needs new migration
Activity
ranjeet150 commentedon Oct 1, 2026
Greetings @maintainers,
I would like to take on and implement this issue:
Persist webhook subscriptions to database instead of in-memory.Technical Implementation Roadmap:
Instance,Persistent,Temporary) with strict TTL management and explicitrequire_authguards.tests/asserting authorized vs unauthorized invocations, mock auth environments, and edge value bounds.I am ready to begin implementation immediately upon assignment and will deliver a high-quality, fully-tested PR. Please assign this issue to me!
feat(webhooks): persist subscriptions in PostgreSQL
woahwhattheheck commentedon Oct 8, 2026
/claim #502
PR #704 is the existing original-author carrier by @woahwhattheheck. Claimant/payee: @woahwhattheheck. Please evaluate this contribution under the issue's existing GrantFox OSS / Third Campaign bounty route.