Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Feature Request: Allow tenant-specific alert URLs in multi-tenant environments

Aperta
  • Qualcosa non va?
#404 6 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@alexluong ci sta già lavorando.

Dal 3/9/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement

Is your feature request related to a problem? Please describe.
Yes. Although Hookdeck Outpost supports multi-tenancy — which is a great fit for our multi-tenant SaaS architecture — the "Alerts" mechanism currently uses a single global configuration for the alert delivery URL (set via environment variable). This means that all alerts for all tenants are sent to the same endpoint, making it difficult to isolate, route, or process alert events per tenant.

Describe the solution you'd like
We would like the alert delivery URL to be configurable per tenant. Ideally, this configuration would be part of the tenant creation/update API so that each tenant can have its own dedicated alert endpoint.

Alternatively, support for URL placeholders in the global alert URL (e.g., using {{tenantid}}) would be helpful:

https://{{tenantid}}.mydomain.com/webhook/alerts

This would allow tenant-specific routing even with a single environment variable, by dynamically resolving the URL based on the tenant ID associated with the failed webhook.

Describe alternatives you've considered
Currently, we're using a shared alert receiver that parses the destination ID and attempts to route internally based on that, but it's fragile and leads to tighter coupling. Having a clean per-tenant alert URL would simplify our architecture and improve observability.

Additional context
In multi-tenant SaaS scenarios where each tenant has its own infrastructure or integration pipeline, isolating alerts is critical. Allowing tenant-level alert URLs makes the platform much more flexible and production-ready for complex use cases.

Lingua principale
Go
Stelle
1.1k
Fork
70
Merge medio
1g 3h
PR unite (30g)
50

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hookdeck/outpost

Tutte le issue di hookdeck/outpost

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.