-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
Cannot "inject" values for email templates from files #665
Comments
It seems like the
At least that renders the |
So, the last bit was missing:
I think the first bit could probably be docs? The one remaining problem is that the config mentions the following templates:
Is there more? Because I just tried a verification flow and the email includes a code? |
Maybe this could be added to the values file: Following the naming of the directories, you can set any other template, e.g.: --set-file kratos.emailTemplates.verification_code.valid.body=kratos/emails/verification_code.html
--set-file kratos.emailTemplates.verification_code.valid.plainBody=kratos/emails/verification_code.txt
--set-file kratos.emailTemplates.verification_code.invalid.body=kratos/emails/verification-invalid.html
--set-file kratos.emailTemplates.verification_code.invalid.plainBody=kratos/emails/verification-invalid.txt |
Hi there! |
Yeah, another example and maybe a link to kratos source would be sufficient IMHO. |
Preflight checklist
Ory Network Project
No response
Describe the bug
I am trying to customize the email templates using external files as the values file from your helm chart gets longer and longer, and longer.
So far, I only get a config map rendered that contains the values from the file though, e.g.
{{.Values.email_recovery}}
but I expected to see the values of the files I inject with--set-file
.Reproducing the bug
I tried it with:
This renders a config map like:
Relevant log output
Relevant configuration
No response
Version
0.37.0
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Kubernetes with Helm
Additional Context
No response
The text was updated successfully, but these errors were encountered: