Subject Request Events and Logs Section

[TheAndrewJackson]

Purpose

Add Events and Logs to the Subject Request Details page. This PR implements everything that's possible right now. In order to finish out the whole issue the backend needs to add some additional logs for the activity timeline. This is a stop gap to merge in what's currently working. Once the backend has added everything that's needed a followup PR will finish this feature.

Changes

• Add Events and Logs section to the subject request details page
• Add slide out drawer to view dataset collection logs and errors.

Checklist

• Update CHANGELOG.md file
  • Merge in main so the most recent CHANGELOG.md file is being appended to
  • Add description within the Unreleased section in an appropriate category. Add a new category from the list at the top of the file if the needed one isn't already there.
  • Add a link to this PR at the end of the description with the PR number as the text. example: #1
• Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram.
• If docs updated (select one):
  • documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
  • documentation issue created (tag docs-team to complete issue separately)
• Good unit test/integration test coverage
• This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
• The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket

Fixes #495

[seanpreston]

Hey @TheAndrewJackson, what data have you been using to test this? Did you write a script or are you running requests through and using the logs? Just thinking a script might help because we can be sure it covers every edge case.

[TheAndrewJackson]

I've been manually creating, or mocking, some of the data on the frontend. I created the execution logs by following the "Minimum API calls to create an Access Privacy Request" directory in our Postman collection.

I agree that a script would be really helpful. Maybe the test-data script could be updated to add logs to each example subject request.

[seanpreston]

Did we think about having this popover update the URL? I could imagine a user wanting to share event logs for request failures for instance, as that's where the trace will be.

[TheAndrewJackson]

I don't think so. That's a good idea but it won't work right now because our current BE router isn't able to resolve dynamic urls. Once we decide on a solution for dynamic urls we will be able support features like this.

Are you okay with adding this in a future PR once that BE supports this?

[seanpreston]

Sure! Have made a ticket

[seanpreston]

Thanks @TheAndrewJackson — LGTM once we've addressed that question on the URLs

[seanpreston]

I agree that a script would be really helpful. Maybe the test-data script could be updated to add logs to each example subject request.

We'd need to actually process the requests created, which means we'll need to run the server (rather than just access the DB directly). I'll have a play around this morning and see if that's an easy enough restructure.

More broadly we need to get better at planning test data in for these frontend features.