Template management service and APIs #2110
Description
Current limitation
Thunder has support for defining templates for different email and SMS delivery scenarios. However, these templates can only be defined as file-based resources (declarative resources) and loaded at startup. There is no backend management service or API for CRUD operations on templates, and no UI for managing them. This limits flexibility and makes it difficult to update templates dynamically or provide versioning.
Suggested improvement
- Onboard backend management services and APIs for CRUD operations (create, read, update, delete, list) for templates (email/SMS, etc.)
- Support versioning of templates (optional, needs discussion)
- Migrate existing file-based templates to the new management system