The Group Mailer aggregates groups, so it can handle more fine-grained email requests

[akjones]

v0 of the email feature only supports emailing the entire organisation. This adds support for emailing a specific group.

The group mailer will need to track any event that effects group membership. This will include both member- and group-related events.

WHEN I send an email to @my-rr.com, THEN the email should be sent only to members of that group.

[pameck]

Story Kick-off

This card is part of the feature Email a Group.

• [x] Split the group-mailer repo, one for the group mailer, and one for the group-mailer-receiver
• [x] Create pipeline for the group-mailer
• [x] dockerise it
• [ ] Create pipeline for the group-mailer-receiver
• [ ] Receive the POST request for the send-email event
• [ ] Validate the sender has the right permissions to send the email
• [ ] Find the group associated with group-email-address
• [ ] Find the emails of the members who belong to the group
• [ ] Put the command event send-email onto the stream
• [ ] Deploy an event-forwarder so the service can listen to group/members related events
• [ ] Listen to group/members related events to keep the state of groups and members up to date.
• [ ] Create a consumer contract tests suite to add to the group-mailer-receiver pipeline.

For reference:

[akjones]

The original scope of this story didn't include sending the email - that was left up to #141, assembling the state of the world and sending the email were thought to be independent enough that the work could be parallelised. Also work related to the group-mail-receiver should be part of that story.

[akjones]

The group-mailer should also provide some kind of consumer driven contract files for the group-mail-receiver to integrate into its pipeline so we can make the coupling between the apps explicit.

[pameck]

@akjones the story does not include the email itself, it does put an event back on the stream to make the mailer service send the emails. Also I'm adding the contract test task!

[camjackson]

This issue is being pushed back as part of a future email milestone. See #160 for what's being done now.