LG-16298 bug fix for Create Job to Track Deletion Workflow Drop-offs#12277
LG-16298 bug fix for Create Job to Track Deletion Workflow Drop-offs#12277kevinsmaster5 merged 10 commits intomainfrom
Conversation
vrajmohan
left a comment
There was a problem hiding this comment.
Also, why is the changelog under OneAccount?
There was a problem hiding this comment.
Why a SQL query? Why not https://guides.rubyonrails.org/active_record_querying.html#and-conditions?
There was a problem hiding this comment.
I referred to prior art with this worker job https://github.com/18F/identity-idp/blob/main/app/jobs/grant_account_reset_requests_and_send_emails_job.rb#L31-L39 using SQL. I assumed it was more efficient to use a SQL query.
There was a problem hiding this comment.
The ticket calls for a separate field in the model called expired_at? Why are we using cancelled_at, which would denote a cancellation by user as opposed to the system?
There was a problem hiding this comment.
As discussed in Slack. Determined that the *_at database change is not needed to accomplish the intent of the story.
There was a problem hiding this comment.
Why is this required? Ditto for lines 20, 29 and 30.
There was a problem hiding this comment.
This seems to be a very weak statement of the expected behavior. Wouldn't "it expires requests with expired grant tokens and ignores valid grant tokens" be better?
There was a problem hiding this comment.
You are correct, that's a much better statement. Thank you!
ecc86e1
ecc86e1 to
3ea8f36
Compare
…PR for deletion workflow
5cea3b1 to
bc6b569
Compare
🎫 Ticket
Link to the relevant ticket:
LG-16298
🛠 Summary of changes
Resolves the timing logic behind the job created with #12187
Adds more comprehensive testing.
📜 Testing Plan
account_reset_wait_period_days: 0Keep the 2 browser tabs with the simulated email open