scheduling: operator reads and actions for dead-lettered outbox work and hook deliveries

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
22/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
nodejs, python, rust

调研方向

Start from crates/registry-scheduling/src/hooks.rs, where hook deliveries are captured with operator_replay: false, then inspect the Scheduling outbox schema and how schedulingctl intents lists items. Compare the existing operator routes in other products for the list/detail/action shape before adding the outbox and hook-delivery reads. Done means both read routes with state, age and cursor paging; one-item actions with reason and idempotency key; audit under the named operator; and Rust/Node/Python client methods.

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

描述

Dead-lettered and expired Scheduling outbox work can be seen only in the database. Nothing can retry or discard it.

Today

  • Reminders, observer-hook delivery and retention run as outbox work. Dead-lettered and expired outbox rows, and dead-lettered hook deliveries, have no route or command.
  • Hook deliveries are captured with operator_replay: false (crates/registry-scheduling/src/hooks.rs). Replay is off by design today, so this issue needs a decision on whether operator replay is allowed.
  • schedulingctl intents lists, but cannot act.

Ask

Read routes:

  • Outbox work by kind and state, including dead-lettered and expired.
  • Observer-hook deliveries by state.

Actions, after the reads:

  • Requeue or discard a dead-lettered outbox item.
  • Replay a dead-lettered hook delivery, if replay is allowed.

Shape

These routes follow the same shape as the other products' operator routes. It is a convention, not a shared contract:

  • A list of held or failed work with state, age and cursor paging, plus a detail read.
  • Actions only after the reads ship. Each action takes one item at a time, with a reason and an idempotency key. The product's own access profile authorises it for a named person's token, and the audit records it under that person.
  • Maintained client methods (Rust, and the Node and Python facades) in the same change.
  • An operator disclosure profile. The routes return identifiers, states, ages and failure classes, not record content or personal data.
  • Security review notes in the pull request, because each route widens what an operator token can read or change.
主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

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

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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