Email settings not picked up when set through environment variables

[jan-pieter]

Affected module Backend

Describe the bug When using environment variables to supply the email configuration the values are not picked up by the backend. No emails are being sent and the UI shows emails being disabled.

To Reproduce

Set the following environment variables:

• OM_EMAIL_ENTITY
• OM_SUPPORT_URL
• AUTHORIZER_ENABLE_SMTP (to true)
• OPENMETADATA_SERVER_URL
• SMTP_SERVER_ENDPOINT
• SMTP_SERVER_PORT
• SMTP_SERVER_USERNAME
• SMTP_SERVER_PWD
• SMTP_SERVER_STRATEGY
• OPENMETADATA_SMTP_SENDER_MAIL

Next, configure an alert and trigger an action that would send out an email. No email is sent. Also, check the Email settings in the UI; the settings configured through environment variables are not present.

Expected behavior Email being sent

Version:

• OpenMetadata version: 1.1.4

Additional context When configuring the email settings through the UI it does work.

[harshach]

@jan-pieter please use the Settings -> OpenMetadata -> Email to configure the email settings. @mohityadav766 are we still supporting env variables to configure email?

[cberge908]

Hi - I was facing the same situation and was about to create a new issue for this.

The environment variables seem to be generated by the helm chart: https://github.com/open-metadata/openmetadata-helm-charts/blob/main/charts/openmetadata/templates/secrets.yaml#L121-L140

Question is if this should simple be removed from the helm chart, with the reference to set this via UI only @harshach?

/edit: Sending mails via the settings from the UI works perfectly fine in 1.3.0.

Cheers, @cberge908

[mohityadav766]

As per discussion, we are going to add a option to sync the Email Settings, and use operation script to invoke the sync process to the DB from the ENV VARS set. cc @harshach @tutte

[cberge908]

Would this be a bi-directional sync or would the ENV vars overwrite the settings made in the UI previously (or vice-versa)?

[datapopcorn]

Hi, is there any update for this issue?