Hi 👋 A bit of a feedback from configuring email delivery on production project in Ory Network: • In HTTP mode building a correct Jsonnet function in “Action HTTP body” is not for the faint of heart. It’s a tedious process of trial and error with no means to debug. The default template gives some insight into the actual contents of

ctx

, but that’s all you have. The documentation is scattered around several pages, and it takes an effort to build a full mental model of it (or maybe I’m just tired). • In HTTP mode

ctx

only has a

text/plain

version of the email, so if you want to send

text/html

(it’s already there in default templates!) you have to use SMTP. And, again, it takes time to debug and come to this realisation. • Trying to edit and save “Action HTTP body” in HTTP mode, you’re asked to provide the Key value for authorisation, even if the UI shows “Stored secret”. It’s extremely annoying, and may be a blocker for those who don’t have access to the API tokens to re-enter. Note: this only happens if you leave the configuration UI and get back to it. It does not reproduce when staying on the same page. On the upside, the SMTP configuration was a breeze, can’t complain 😅

> • Trying to edit and save “Action HTTP body” in HTTP mode, you’re asked to provide the Key value for authorisation, even if the UI shows “Stored secret”. It’s extremely annoying, and may be a blocker for those who don’t have access to the API tokens to re-enter. Note: this only happens if you leave the configuration UI and get back to it. It does not reproduce when staying on the same page. > I had the same issue. It’s very annoying and could produce some big problems after minor changes.

Thanks a lot for the great & detailed feedback! I agree that this can be improved - will forward it to the team 🙏