feat: route account activation emails via SES using waffle flag #37932
+29
−0
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
nthriveni-sonata-ship-it
force-pushed
the
feature/account-activation-ses-routing
branch
from
c9a9d9a to
a363016
Compare
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 introduces a waffle-flag–controlled routing for Account Activation emails to be sent via SES.
What’s included:
Added a waffle flag to control SES routing for account activation emails
Updated activation email composition to override the default ACE channel to django_email when the flag is enabled
Local devstack validation using a file-based email backend to verify channel override and email generation
Testing:
Verified waffle flag behavior locally via Django admin
Confirmed ACE message options include transactional and django_email channel override
Validated rendered email output using the file-based email backend
Next steps:
– Draft PR for early review and alignment