Webhooks admin half (A-36)

Abierto
#3,424 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C#
Estrellas
567
Forks
107
Merge medio
1 h 19 min
PR fusionados (30 d)
353

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.