BReg: a read route for the hook delivery state of a record
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- openapi, rust
调研方向
Read the existing hook delivery and access profile behavior, then inspect the generated API contract and the profile model in explain; the issue does not name specific source or test files. Add a read route scoped to records and hook names the caller may access, returning only hook name, time, and delivery state. Done when the route is in the generated contract, profile behavior is covered in explain, and tests verify access refusal and dead-letter output excludes payload values and destinations.
由索引模型根据 Issue 内容生成。
描述
Problem
After a record changes, BReg delivers hooks on a best-effort basis; a failed delivery ends as a dead letter. Only an operator sees it, through bregctl hook list. A service that sends a payment instruction after a change cannot tell the people working the record that the instruction never left, because there is no public route and no application surface for it.
Smallest change
- A read route that returns, for one record the caller may read, the delivery state of the hooks it caused: pending, delivered, or dead-lettered, with the hook name and time, and nothing from the payload.
- Scoped by the caller's access profile: a profile sees the state only for records and hook names it is granted.
- A follow-up in App Kit can show a banner from it; that is a separate change in the kit repository.
Acceptance
- A profile granted the record can read its hook delivery state, and a profile not granted it is refused with the usual problem.
- A test shows a dead letter surfacing as dead-lettered with no payload value and no destination in the answer.
- The route appears in the generated API contract and is covered by the profile model in
explain.
Out of scope
- Replay or discard from the route (operators keep
bregctl hook). - Delivery state for other products' outboxes.
- The App Kit banner.
Related
- #2129, #2204
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 151
环境准备
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
registrystack/registry-stack 的其他 Issue
-
area:breg enhancement
难度 2/5 1-3 小时 新手友好度 65/100
registrystack/registry-stack#2765 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
registrystack/registry-stack#2761 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
registrystack/registry-stack#2743 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
registrystack/registry-stack#2706 ·
维护者通常 1 天内回复
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directory未关闭
难度 2/5 1-3 小时 新手友好度 83/100
registrystack/registry-stack#2704 ·
维护者通常 1 天内回复
查看 registrystack/registry-stack 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 82/100
stackabletech/airflow-operator#898 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)可能已有人在做 @zyl71 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100