[MGNLHOOK-2] Configure a webhook Created: 12/Apr/22 Updated: 27/Apr/22 Resolved: 21/Apr/22 |
|
| Status: | Closed |
| Project: | Magnolia Webhooks |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Javier Benito | Assignee: | Javier Benito |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | |
| Epic Link: | Configure a Webhook |
| Sprint: | DevX 8 |
| Story Points: | 2 |
| Description |
User Story:As a developer I want to configure a webhook so that I can supply a webhook to the system. Further details:From Subtask: SP: 2
The main goal of this task, is to have a Magnolia Registry in place for Webhook definitions, which would be done using Light Development (yaml file), without the events definition or the target endpoint parts (as they will be done in other task), following the example provided here Magnolia should read a webhook definition file in a light module, probably under a webhooks named folder, with this initial content:
description: Do something after the publication of a page
enabled: true
We should provide a way to detect that further changes are related to the same webhook, maybe using the file name as a key, or providing a parameter inside the definition. |