Vanotify migrate simple_forms_api to use v2 email job#27787
Merged
nathanbwright merged 5 commits intomasterfrom Apr 21, 2026
Merged
Vanotify migrate simple_forms_api to use v2 email job#27787nathanbwright merged 5 commits intomasterfrom
nathanbwright merged 5 commits intomasterfrom
Conversation
…_forms_api/notification/email.rb to use v2 email job
…_forms_api/notification/form_upload_email.rb to use v2 email job
dominicpadula1
previously approved these changes
Apr 20, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR migrates Simple Forms API notification email delivery to the VANotify V2 queuing job, adding support for scheduled sends via a new VANotify::V2::QueueEmailJob.enqueue_at entrypoint and gating the behavior behind new Flipper toggles.
Changes:
- Added
VANotify::V2::QueueEmailJob.enqueue_atand unit tests for it. - Updated SimpleFormsApi notification services to use V2 (immediate + scheduled) when the new Flipper flags are enabled.
- Added new feature toggles for SimpleFormsApi V2 email behavior in
config/features.yml.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| modules/va_notify/app/sidekiq/va_notify/v2/queue_email_job.rb | Adds enqueue_at helper to schedule V2 queued emails. |
| modules/va_notify/spec/sidekiq/v2/queue_email_job_spec.rb | Adds specs covering enqueue_at behavior and validation paths. |
| modules/simple_forms_api/app/services/simple_forms_api/notification/form_upload_email.rb | Switches scanned form upload notifications to V2 when flipper is enabled (now + scheduled). |
| modules/simple_forms_api/app/services/simple_forms_api/notification/email.rb | Switches standard SimpleFormsApi notifications to V2 when flipper is enabled (now + scheduled for form-data path). |
| modules/simple_forms_api/spec/services/notification/form_upload_email_spec.rb | Adds coverage for V1 vs V2 behavior under the upload-email flipper (now + scheduled). |
| modules/simple_forms_api/spec/services/notification/email_spec.rb | Adds coverage for V1 vs V2 behavior under the email flipper (now + scheduled). |
| modules/simple_forms_api/spec/requests/simple_forms_api/v1/simple_forms_spec.rb | Stubs new flipper off to keep request spec behavior on V1 by default. |
| config/features.yml | Adds new Flipper entries for SimpleFormsApi V2 email migrations. |
rmtolmach
reviewed
Apr 20, 2026
Contributor
|
@nathanbwright a few small questions ☝️ |
7545a13
rmtolmach
approved these changes
Apr 21, 2026
Contributor
rmtolmach
left a comment
There was a problem hiding this comment.
only small changes since your last team approval, so I'll approve ✅
balexandr
pushed a commit
that referenced
this pull request
Apr 21, 2026
* Migrate perform_async in modules/simple_forms_api/app/services/simple_forms_api/notification/email.rb to use v2 email job * Migrate perform_async in modules/simple_forms_api/app/services/simple_forms_api/notification/form_upload_email.rb to use v2 email job * Create enqueue_at method and migrate simple_forms to use it with v2 email job * Clarify flipper description * Scope flipper stubbing
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
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.
Keep your PR as a Draft until it's ready for Platform review. A PR is ready for Platform review when it has a teammate approval and tests, linting, and settings checks pass CI. See these tips on how to avoid common delays in getting your PR merged.
Summary
VANotify::V2::QueueEmailJob.enqueue_at.Related issue(s)
Testing done
Screenshots
Note: Optional
What areas of the site does it impact?
(Describe what parts of the site are impacted andifcode touched other areas)
Acceptance criteria
Requested Feedback
(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?