-
Notifications
You must be signed in to change notification settings - Fork 367
fix: mount notification email templates #4755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
fix: mount notification email templates #4755
Conversation
Pull Request Test Coverage Report for Build 21596281528Details
💛 - Coveralls |
|
@sweatybridge sorry for the tag, would you mind taking a look at this as well? A couple of users are stuck on it. Also, kind of related: supabase/supabase#41860 (comment), its about how auth template paths (if not absolute) are expected to be relative to a level above Lines 697 to 710 in 3fe548f
|
What kind of change does this PR introduce?
Bug fix #4783
Follow up: #4400
What is the current behavior?
When running
supabase start, only auth email templates were mounted in kong and configured in auth service.Notification email templates were ignored.
What is the new behavior?
Notification email templates are now mounted in Kong, and the required env vars for notification templates are configured in the auth service.