Feature Request: Allow tenant-specific alert URLs in multi-tenant environments
维护者通常 1 天内回复
@alexluong 已经在做这个了。
开始于 2025年9月3日。
评估
这个 Issue 还没有评估数据。
描述
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.
- 主要语言
- Go
- 星标
- 1.1k
- 派生
- 70
- 平均合并
- 1 天 18 小时
- 30 天内合并 PR
- 56
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
hookdeck/outpost 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 48/100
hookdeck/outpost#1117 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
维护者通常 1 天内回复
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
superplanehq/superplane#8604 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
documentation hacktoberfest priority: low skill: good first issue status: ready for dev
难度 2/5 半天 新手友好度 85/100
hyperledger-labs/fabric-smart-client#2142 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
numberly/vault-db-injector#107 ·
维护者通常 1 天内回复