Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Config overrides at more granular levels

未关闭
#582 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
go

调研方向

The issue names no files, tests, or code entry points. Start by locating where deployment-level configuration is defined and how tenant and destination settings are represented; then identify which settings should support overrides and how precedence should work. Done means the intended override scope and behavior are agreed on, but the issue does not specify them.

由索引模型根据 Issue 内容生成。

描述

enhancement

Is your feature request related to a problem? Please describe.
Not related to any particular problem.

Describe the solution you'd like
Currently, most of available configuration is managed at the deployment level (e.g. retries, timeouts, etc.). However, as we look more towards a multi-tenant world, enabling more granular configuration would be invaluable and give users more flexibility per tenant.

With that in mind, adding configuration (where applicable) overrides at the tenant and destination level will enable better support for a larger user base.

Describe alternatives you've considered
In theory, we could do multiple deployments of Outpost (per tenant), but this seems to defeat the purpose of the multi-tenancy support that Outpost has.

Happy to discuss other suggestions too!

主要语言
Go
星标
1.1k
派生
70
平均合并
1 天 18 小时
30 天内合并 PR
56

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

hookdeck/outpost 的其他 Issue

查看 hookdeck/outpost 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。