Hi @Shruthii7, thank you for showing interest in this proposal.
Should the API support fetching templates from external repositories directly (e.g., Git-based), or would it be better to introduce an intermediate storage/cache layer?
I don’t think that’s necessary. The templates can be posted/registered as part of the MB/LB deployment scripts. The mail service can cache them locally (e.g., in a Docker volume) so that they’re readily available if the container is restarted.
Are there preferred constraints regarding authentication and template validation?
The mail service isn’t accessible from outside our private network, and I think it’s a good idea to keep it that way. Project admins can just use the API via SSH tunnel.
What constraints did you have in mind re: template validation?
Should template loading be runtime-dynamic (hot reload) or version-controlled through explicit updates?
The latter is what I had in mind (but it should probably be possible to forcefully update an existing version in case a hotfix is needed). Can you explain what you had in mind with “runtime-dynamic (hot reload)”?
Are there existing architectural decisions from last summer’s project that I should align with?
Not sure how to best answer this one, because I wouldn’t expect the architecture to change significantly, but @JadedBlueEyes might have a better answer.