Open sastels opened 5 months ago
This PR will allow us to use pinpoint for a few templates and SNS for the rest https://github.com/cds-snc/notification-api/pull/2184
PR merged. Currently (and tested) in staging:
After we release this to prod we will set values for prod AWS_PINPOINT_SC_POOL_ID
and AWS_PINPOINT_SC_TEMPLATE_IDS
. This will bring production to the same state as staging (Pinpoint for certain templates, SNS for the rest).
PR merged. Currently in staging (and tested) :
After we release this to prod we will turn on the shortcode pool in production: https://github.com/cds-snc/notification-manifests/pull/2652
I have added the production shortcode to the shortcode pool. This required updating the pool keywords to be the same as the shortcode keywords (to add a number to an existing pool the keywords must agree).
The shortcode pinpoint delivery receipts and the longcode delivery receipts are different. Merged and tested in staging: https://github.com/cds-snc/notification-api/pull/2189
Next step: release to prod tomorrow and test there.
The short code doesn't send back the same responses as long codes, and we had to make a change that will be released today.
short code delivery receipts processed correctly now :tada:
@ben851 to QA
Sent two messages, verified that pinpoint was sent by pinpoint, and the other was sent by SNS.
Description
As a Notify user, I need my SMS to be sent from the appropriate numbers
WHY are we building?
We have brought the pinpoint code back into the code base and it seems to be working. We will now enable it in production.
WHAT are we building?
Turn on Pinpoint code in production.
VALUE created by our solution
Will be able to restrict shortcode usage.
Acceptance Criteria
QA Steps (in production)