feat: add AWS_PINPOINT_DEFAULT_POOL_ID variable to k8s and set in staging #2627
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What happens when your PR merges?
What are you changing?
Provide some background on the changes
Following cds-snc/notification-api#2173, we add the new
AWS_PINPOINT_DEFAULT_POOL_ID
variable to k8s.Note that in production (where
AWS_PINPOINT_SC_POOL_ID
andAWS_PINPOINT_DEFAULT_POOL_ID
are not set) we will still fall back to SNS.Checklist if making changes to Kubernetes: