This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Unify ExecutionLog and AuditLog into a single endpoint with grouping at request level
#1024
Assignees
Labels
enhancement
New feature or request
Comments
10 tasks
TheAndrewJackson
pushed a commit
that referenced
this issue
Aug 15, 2022
…1068) * Update the request status endpoint, so when the verbose query param is used and execution logs are embedded, also return audit logs. Execution Logs are created at the collection level while audit logs are for the overall privacy request level, so most fields returned for audit logs are None. Logs are also grouped at the dataset level here, so give the audit logs a fake dataset name for display purposes, for example, "Request approved". * Update CHANGELOG and update docs to reflect that audit logs are included in a verbose request status response.
sanders41
pushed a commit
that referenced
this issue
Sep 22, 2022
…1068) * Update the request status endpoint, so when the verbose query param is used and execution logs are embedded, also return audit logs. Execution Logs are created at the collection level while audit logs are for the overall privacy request level, so most fields returned for audit logs are None. Logs are also grouped at the dataset level here, so give the audit logs a fake dataset name for display purposes, for example, "Request approved". * Update CHANGELOG and update docs to reflect that audit logs are included in a verbose request status response.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
In designs we want to give a time series of the life of a subject request. This includes both submitted, approval info and execution level information.
To support our front end users and organize the information well, we need to unify/combine this information into a single endpoint.
Notes
The text was updated successfully, but these errors were encountered: