-
Notifications
You must be signed in to change notification settings - Fork 72
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
Updating privacy request search endpoint #4987
Updating privacy request search endpoint #4987
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Passing run #8359 ↗︎
Details:
Review all test suite changes for PR #4987 ↗︎ |
…request-fields-and-identities
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4987 +/- ##
==========================================
+ Coverage 86.51% 86.54% +0.02%
==========================================
Files 351 351
Lines 21693 21738 +45
Branches 2872 2878 +6
==========================================
+ Hits 18768 18813 +45
Misses 2420 2420
Partials 505 505 ☔ View full report in Codecov by Sentry. |
…request-fields-and-identities
@galvana can you make sure unit tests are running over here before I start a review? |
…request-fields-and-identities
Thanks for helping with the numpy changes and getting tests passing on this branch @galvana 👍 starting review now - |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some additional documentation requested if you agree with me there - really nice PR
Passing run #8360 ↗︎
Details:
Review all test suite changes for PR #4987 ↗︎ |
Closes PROD-2124
Description Of Changes
Marked the existing
GET /privacy-request
as deprecated in favor of a newPOST /privacy-request/search
endpoint. We needed to specify custom identities and custom privacy request fields but these inputs are a combination of identity/custom field name or and value. I first thought of supporting dynamic query params but that didn't work out since we need to make a distinction if the new query param is an identity or a custom field lookup.I also made the decision to include the identity or custom field name for the search to be more specific. The current
GET /privacy-request
endpoint just matches on the identity value without considering which identity type the result matched on.The new endpoint also removes the single string query param of
identity
in favor of anidentities
value in the POST body.The
external_id
field is still supported as a standalone field, for backwards compatibility, even though we supportexternal_id
as a default identity type as wellCode Changes
POST /privacy-request/search
endpoint andPrivacyRequestFilter
schema to validate the payload.Steps to Confirm
FIDES__EXECUTION__ALLOW_CUSTOM_PRIVACY_REQUEST_FIELD_COLLECTION=true
in your.env
file to enable custom privacy request field collectionPre-Merge Checklist
CHANGELOG.md