Localstack: aws ses - view email contents

Created on 5 Jun 2020  路  3Comments  路  Source: localstack/localstack

It looks like moto provides the ability to view the email raw contents which are sent via ses

https://github.com/spulec/moto/issues/1392

this came up in https://github.com/localstack/localstack/issues/339 as a feature request

amirsaber localstack uses moto to mock SES service and it doesn't actually send email. It receives API call to send email and just stores it in memory and sends successful response back. Would be nice to have something like Inbox in Dashboard where you can see list of sent emails.

鈹咺ssue is synchronized with this Jira Bug by Unito

Most helpful comment

A way to retrieve the requests programattically would be enough, since this is used from integration tests the most (I assume). I'd caution against actually sending the emails as the title says, this is a mock afterall.

All 3 comments

A way to retrieve the requests programattically would be enough, since this is used from integration tests the most (I assume). I'd caution against actually sending the emails as the title says, this is a mock afterall.

A way to retrieve the requests programattically would be enough, since this is used from integration tests the most (I assume). I'd caution against actually sending the emails as the title says, this is a mock afterall.

agreed @YarekTyshchenko , title updated. 馃憤

For my use case, i would like my testers to be able to view the email content as rendered by a client, when they are running our full project setup locally. this plugin looks like it would solve that use-case. https://github.com/csi-lk/aws-ses-local - its a bit old and doesn't support rawemail so i would need to give it a little love :)

but for localstack, a way to retrieve the requests programmatically would benefit my devs developing in asserting the generated email contents

For my use case, i would like my testers to be able to view the email content as rendered by a client, when they are running our full project setup locally

A common use case I imagine. I'm hoping that exposing the contents programatically means you (or anyone really) can throw a simple container in that renders them, and it doesn't put the implementation burden on localstack. Dividing problems and all that.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bobtiernay-okta picture bobtiernay-okta  路  3Comments

orr-levinger picture orr-levinger  路  3Comments

Deblob12 picture Deblob12  路  3Comments

burm87 picture burm87  路  3Comments

Noah-Vivial picture Noah-Vivial  路  3Comments