feat: enable SES routing for account activation emails in production#265
Open
nthriveni-sonata-ship-it wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR enables routing of account activation emails through AWS SES in production using a waffle flag.
The changes are cherry-picked from previously validated Stage implementation and include:
SES-based email routing controlled via user_authn.enable_ses_for_account_activation waffle flag
Fallback to default ACE channel in case of SES delivery failure
Minimal changes scoped to tasks.py following review feedback
Validation
Successfully tested in Stage:
Account activation emails sent via SES when flag is enabled
Fallback behavior verified
No impact on registration or activation flow
Notes
Feature is controlled via waffle flag and can be safely enabled/disabled in Production
No changes outside account activation email flow
@jsnwesson - could you please look into this PR