Skip to content
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

BE: Update Privacy Request API endpoints (Get Request Status Logs & Get Request Status) to include Datastore connection key #1725

Closed
chriscalhoun1974 opened this issue Oct 31, 2022 · 1 comment · Fixed by #2100
Assignees

Comments

@chriscalhoun1974
Copy link
Contributor

chriscalhoun1974 commented Oct 31, 2022

USER STORY

For the DSR Error Handling Q4 deliverable, there is a requirement to update the error detail and log when a DSR encounters an error during processing. This includes where and why the subject request errored at.

REQUIREMENTS

Please reference Display DSR error details and log#1202 for further details.

AC

Update the following API endpoints to include the Datastore connection key:

  • /api/v1/privacy-request/{privacy_request_id}/log
  • /api/v1/privacy-request

DESIGNS

User Flow:
https://www.figma.com/file/4qgQpYc1bX4dXg2PHmRORL/DSR-Error-Handling?node-id=2%3A7179

Final Screens:
https://www.figma.com/file/MTbZohIGvB4bq2f2wkiDHO/Fidesops-Management-UI?node-id=4006%3A60640

@mfbrown mfbrown assigned sanders41 and unassigned eastandwestwind Nov 1, 2022
@chriscalhoun1974 chriscalhoun1974 changed the title Update Privacy Request API endpoints (Get Request Status Logs & Get Request Status) to include Datastore connection key BE: Update Privacy Request API endpoints (Get Request Status Logs & Get Request Status) to include Datastore connection key Nov 1, 2022
@sanders41
Copy link
Contributor

The original plan for this was for the backend to send the stack trace, but the figma screen looks a little different than that. Can we clarify this a bit to make sure we go down the correct path?

@mfbrown mfbrown transferred this issue from ethyca/fidesops Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants