we are looking for a sane way to handle email username/passwords both in development and in testing.
Those secrets should not reside in our version control but rather they should be passed as environment variables, however there are some complexities:
- The camunda BPMN mail core uses as a configuration a plain java old properties file, which doesn’t support using environment variables placeholders (One could use Apache Commons Config, but you would have to re-build the plugn)
- Because the properties are read from file, any property passed to the JVM with -Dmail.some_param will be ignored
What are reasonable ways to handle secrets and environment configuration for unit testing and production when using the connector?