Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor sending consent notifications #1891

Merged
merged 2 commits into from
Oct 1, 2024
Merged

Conversation

thomasleese
Copy link
Contributor

This refactors how we send consent notifications (both requests and reminders) in to a method on the ConsentNotification model which handles creating a record of the notification and sending the notification to all parents, reducing duplicate logic in a number of different jobs.

Base automatically changed from track-consent-emails to main October 1, 2024 16:03
This simplifies how we send the consent notifications to add a method to
the `ConsentNotification` model for sending consent notifications and
reduce the duplication.
This simplifies the jobs for sending consent reminders and consent
requests by combining the jobs in to one. We're now sending the emails
and texts asynchronously, so it effectively the new single job is only
doing the work to queue all the emails, which will then be sent out in
the background meaning combining the jobs shouldn't have an impact on
performance.
@tvararu tvararu temporarily deployed to mavis-pr-1891 October 1, 2024 16:04 Inactive
@thomasleese thomasleese enabled auto-merge (rebase) October 1, 2024 16:04
Copy link

sonarcloud bot commented Oct 1, 2024

@thomasleese thomasleese merged commit 7cc58e3 into main Oct 1, 2024
12 checks passed
@thomasleese thomasleese deleted the consent-notification-send branch October 1, 2024 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants