Recipient list management

[cremich]

Description

A very important feature to support onboarding new tenants will be, to give tenant managers the ability to upload and maintain recipient lists for each test pool. Those recipient lists are basically phone numbers we have to add as endpoints into Amazon Pinpoint. We have to keep in mind, that a phone number can be associated to multiple test pools but will be modeled as one endpoint in Pinpoint. A common use case for example in Kindergartens, where a mom or a dad has two kids in different groups.

Test Pool associations are modeled as endpoint attributes in pinpoint. So in a nutshell, a tenant manager must be able to

• add phone numbers
• associate phone numbers to test pools
• delete phone numbers (in case of a request for deletion)

Fixes #39

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Added api infrastructure unit tests
• Added tests to ensure dynamoDb table is provisioned correctly

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[Bakkenrak]

Do you plan on translating the changes in the recipient list table to pinpoint via DynamoDB streams and then lambda or something similar?

[Bakkenrak]

With the way this is updated the frontend needs to take care of providing the full list of associated pools on an update request, right? When trying to imagine a dialog that would support this I'm wondering if it really fits the pool list management workflow I would prefer as a user.