-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Additional PIR opt out confirmation pixels (#3119)
Task/Issue URL: https://app.asana.com/0/0/1207733131726022/f Tech Design URL: CC: **Description**: I've linked to the implementation task above, but more useful is the proposal task here: https://app.asana.com/0/0/1207999607996551/f Adds new pixels that indicate how long it takes us to confirm successful opt outs This involves adding new fields to the DB, so the migration also needs to be tested Also moves monitoring pixel firing up the stack to the agent manager where IMO it belongs, so special attention needs to be made that nothing is broken there. **Steps to test this PR**: 1. With DBP already setup, confirm via the DB view that OptOutJobs have the new fields (createdDate, submittedSuccessfullyDate, sevenDaysConfirmationPixelFired, fourteenDaysConfirmationPixelFired, twentyOneDaysConfirmationPixelFired). Only submittedSuccessfullyDate should be nil. 1. From a fresh start, set up DBP and confirm via the DB viewer again that everything looks correct 1. Let DBP run for a bit (you could change some background activity values to speed it up) and check that opt out created dates are set correctly and that confirmed opt outs get the correct submittedSuccessfullyDate. 1. You probably don't want to wait 7/14/21 days to test the actual pixel firing, so in DataBrokerProtectionStatsPixels, change one of these to just be true "let hasEnoughTimePassedToFirePixel = submittedSuccessfullyDate.hasBeenExceededByNumberOfDays(14)" (e.g. to "let hasEnoughTimePassedToFirePixel = true") <!-- Tagging instructions If this PR isn't ready to be merged for whatever reason it should be marked with the `DO NOT MERGE` label (particularly if it's a draft) If it's pending Product Review/PFR, please add the `Pending Product Review` label. If at any point it isn't actively being worked on/ready for review/otherwise moving forward (besides the above PR/PFR exception) strongly consider closing it (or not opening it in the first place). If you decide not to close it, make sure it's labelled to make it clear the PRs state and comment with more information. --> **Definition of Done**: * [ ] Does this PR satisfy our [Definition of Done](https://app.asana.com/0/1202500774821704/1207634633537039/f)? --- ###### Internal references: [Pull Request Review Checklist](https://app.asana.com/0/1202500774821704/1203764234894239/f) [Software Engineering Expectations](https://app.asana.com/0/59792373528535/199064865822552) [Technical Design Template](https://app.asana.com/0/59792373528535/184709971311943) [Pull Request Documentation](https://app.asana.com/0/1202500774821704/1204012835277482/f)
- Loading branch information
1 parent
94409e4
commit c9d726f
Showing
19 changed files
with
943 additions
and
76 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.