Please include a summary of the change and why this is needed.
- [Design Document](paste URL here or delete)
- [Jira Ticket](paste URL here or delete)
Please delete options that are not relevant.
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- This change requires a documentation update
- Other - Reason:
- CCPA
- GDPR
- Downstream System A
- Downstream System B
Please describe how to verify this change in production. Through metrics and logs, or manually if necessary.
List any other changes that must be deployed and enabled before deploying and/or enabling this change, if any.
How to debug if there are any issues with this code?
Are there issues with simply rolling this commit back in production?
- Unit
- Functional
- Integration
- End-to-end
- None - Reason:
- My code follows the style guidelines in the file or project
- I have performed a self-review of my own code
- I have commented my code, particularly in hard-to-understand areas
- I have made corresponding changes to the documentation
- I have added tests that prove my fix is effective or that my feature works
- New and existing unit tests pass locally with my changes
- Any dependent changes have been merged and published in downstream modules