Webhooks admin half (A-36)

Aperta
#3,424 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C#
Stelle
567
Fork
107
Merge medio
1h 19m
PR unite (30g)
353

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fluentcms/FluentCMS

Tutte le issue di fluentcms/FluentCMS

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.