Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
EPAM-Veg Sprint 1, EPAM-Veg Sprint 2
-
3
-
Vega
Description
Module description
This module should contain information describing the notification events. The entity will describe the event name, possible delivery channels,
and contain references to templates for each delivery channel and may contain a scheduler configuration for this delivery event. Also module
should provide CRUD REST API for UI. Maybe we need to be able to configure this events metadata from user interface.
Requirements
Create new repository at github and new module mod-event-config with stub REST API
Method | Description |
---|---|
POST /eventConfig | Create new event config in storage |
GET /eventConfig/id | Get event config from storage |
PUT /eventConfig/id | Update event config in storage |
DELETE /eventConfig/id | Delete event config from storage |
{
“id”:”1”,
“name”:”password reset”,
“active”:”true”,
“templates”:[
,
{ “deliveryChannel”:“sms”, “templateId”:”2”, "outputFormat":"text/plain" } ],
“metadata”:
}
implementation of REST API will we in separate story
Acceptance Criteria
- The new module is created
- the module provides stub endpoints which is accessible through OKAPI
- rest tests exists and passed
- github repository exists in folio-org space
- module is included in Jenkins build
- module exists and starts as a docker container within vagrant snapshot images [folio/snapshot, folio/testing, folio/testing-backend]
TestRail: Results
Attachments
Issue Links
- blocks
-
MODEVENTC-2 Add CRUD REST implementation to mod-event-config
-
- Closed
-
- is blocked by
-
FOLIO-1606 Add mod-event-config to CI testing builds
-
- Closed
-
- relates to
-
FOLIO-1371 API Design: A Folio module to send and format emails.
-
- Closed
-