From address cannot be set without an enabled email provider

[bennycode]

Checklist

• I have looked into the README and have not found a suitable solution or answer.
• I have looked into the documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have upgraded to the latest version of this tool and the issue still persists.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

I am using the Auth0 Email Provider (not the Custom Email Provider) and configured some email templates with a from address.

I can download my Auth0 config successfully using a0deploy -c=config.json export --format=yaml but when I want to upload my download this error appears:

2024-12-03T16:10:55.485Z - error: Problem running command import during stage processChanges when processing type emailTemplates
2024-12-03T16:10:55.485Z - error: From address cannot be set without an enabled email provider.

It is surprising that the behaviour is not deterministic (i.e. I can upload what I downloaded).

Expectation

I can upload what I download.

Reproduction

1. Given an email template setup
2. While not having a custom email provider setup
3. Then the upload of the tenant.yaml crashes

Deploy CLI version

8.3.0

Node version

20.17.0

[kushalshit27]

Hi, @bennycode
Thank you for reporting this issue! It seems that there was a bug in the email provider, which is fixed now 'Email Provider'.

Please try version 8.3.0. I would appreciate you test this out and if problem still persists, we can re-evaluate.

[kushalshit27]

Hi, @bennycode,
Issue is generated by emailTemplates due to disabled emailProvider.

This is a validation , if emailProvider is not enabled, it is not allowed to update emailTemplates from key.

You can still update emailTemplates by removing from key-value.

Let me know if you have any questions. Thanks.

[kushalshit27]

Recent updates might have addressed this issue. We are closing it as stale. If the problem persists, please reopen the issue and provide more details. Thanks