Webhooks admin half (A-36)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with docs/planning/admin-technical-spec.md, sections 5.3 and 10.7, then review the existing webhooks routes and the related A-51 and A-33 work. The issue calls for a complete admin area, delivery log and redelivery, secret handling, component and API tests, and an end-to-end case. It is done when the listed acceptance criteria pass; the issue does not name implementation files or test entry points.

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

描述

area:admin type:feature

Problem

Row 3.17 asks that webhooks are managed in the admin. The webhooks plugin has its routes under /webhooks, and its admin half is the stub of A-51: making a webhook, reading why a delivery failed or sending it again takes a direct call.

Proposal

The half FluentCMS.Plugins.Webhooks.Admin (5.3), for a caller who holds webhooks.manage in the site:

  • /webhooks with a menu item: the list, create, edit, enable and disable, delete. The event names a webhook subscribes to are the half's own list, since no answer holds them (1.4).
  • The signing secret: a create that lets the server make the secret answers it once, shown with the copy button of A-33. A new secret on an edit keeps the old one signing for the overlap, and the page shows until when.
  • Header values are secrets and never come back. A stored value is kept only while the scheme, host and port of the URL stay as they are; a change of them answers FCMS1560 on headers.{name}. So when the user changes the address, the form asks for each header's value again before the save.
  • /webhooks/{id}: the delivery log, read in pages, with status, duration, body and answer; redeliver one; ping.
  • The half's records are checked against the OpenAPI document.

Acceptance

  • An administrator makes a webhook for a publish event, copies the secret made for it, and the secret cannot be read again
  • A publish shows as a delivery with its status, body and answer, and a failed one is sent again
  • A change of the address asks for each header's value again, and a save without them shows the refusal on the header
  • A ping shows its result
  • In a site where the plugin is disabled the pages and the menu item are absent, and the half is not fetched
  • Component tests cover the form, the headers and the log; the API tests check the records against the OpenAPI document; an end-to-end case makes a webhook against a receiver of the test and reads its delivery

Design: docs/planning/admin-technical-spec.md, sections 5.3 and 10.7 (A-36). Row 3.17. Needs A-51, and A-33 for the secret shown once; #3104 is merged. Size: M.

主要语言
C#
星标
567
派生
107
平均合并
1 小时 19 分钟
30 天内合并 PR
353

环境准备

从这里开始

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

fluentcms/FluentCMS 的其他 Issue

查看 fluentcms/FluentCMS 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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