Move email templates to disk

[phavekes]

Currently, the email templates used for emails to users are stored in the database during a push to https://{{ middleware_vhost_name }}/management/configuration. Since these change only rarely, we are moving them to disk.

• The templates are stored in /config/openconext
• Default values are included in the repo and the tars, which can be overwritten during (Ansible) deployment
• Templates on disk take precedence over the values in the database configuration
• Empty or missing templates in the database or config-push do not trigger error messages or warnings

[pmeulen]

Templates on disk take precedence over the values in the database configuration

I think the new MW version can just ignore the email templates in the database, and always read them from disk. A backward-compatibility mechanism seems unnecessary here.

Empty or missing templates in the database or config-push do not trigger error messages or warnings

Yes, they should be allowed to be there for backward-compatibility reasons, but must be ignored. This means that updating the email templates using an API is no longer possible.

[phavekes]

Extra attention is needed for:

• Does every push add an event to the stream? Even if there are no changes?