ENG-2435: Add privacy requests diagnostics endpoint#7332
Merged
nreyes-dev merged 13 commits intomainfrom Feb 23, 2026
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Contributor
Greptile SummaryThis PR adds a new diagnostics export endpoint ( Key changes:
Concerns:
Confidence Score: 4/5
Important Files Changed
Last reviewed commit: 0e6b568 |
galvana
approved these changes
Feb 23, 2026
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.
Ticket ENG-2435
Description Of Changes
Adds a new endpoint to export a non-PII diagnostics JSON for a single privacy request ID.
Code Changes
Steps to Confirm
In /docs, hit either:
GET /api/v1/privacy-request (list), or
GET /api/v1/privacy-request/search
Copy an id from the response.
In /docs:
GET /api/v1/privacy-request/{privacy_request_id}/diagnostics
Paste the privacy_request_id
Execute
Expect 200 and a PrivacyRequestDiagnostics JSON payload.
Call the same endpoint with a bogus ID.
Expect 404 with a “No privacy request found…” detail.
Pre-Merge Checklist
CHANGELOG.mdupdatedmaindowngrade()migration is correct and works