Skip to content

SES Provider #64

Closed
Closed
@woutercouvaras

Description

@woutercouvaras

New Feature / Enhancement Checklist

Current Limitation

I love the design of this module. Because of the smart design, running a custom provider is pretty easy, but I was wondering if you would like an SES converter? I've already built it and updated docs and ready to do a PR.

Feature / Enhancement Description

Simply adding an SES Payload Converter, with additions to docs to explain useage.

Example Use Case

Sending system emails via AWS SES.

Alternatives / Workarounds

The custom api support it totaly viable, so this is not strictly necessary, I just thought it might be nice to bake it into the package, but that could create additional noise, so I'm totally happy if you shut this down :D

3rd Party References

No really applicable, I don't think?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions