feat(projectHistoryLogs): add endpoints for viewing project history logs TASK-973 #5319
+814
−19
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.
🗒️ Checklist
<type>(<scope>)<!>: <title> TASK-1234
frontend
orbackend
unless it's global📣 Summary
Add two new endpoints for viewing project history logs, one for all logs, and one for logs for a given project.
📖 Description
Adds two new endpoints:
/api/v2/project-history-logs
(all project history logs) and/api/v2/assets/<uid>/history
(logs for the specific project).The former is only available to superusers, the latter is available to anyone with the manage_asset permission for the project.
Both endpoints can be searched by a all fields, most importantly
action
,metadata__asset_uid
, andusername
. A full list of available searchable fields is in the endpoint documentation.👀 Preview steps
Feature/no-change template:
localhost/api/v2/project-history-logs
localhost/api/v2/project-history-logs
. You should get a 401.localhost/api/v2/project-history-logs
. You should get a 403.localhost/api/v2/assets/<asset_uid>/history
localhost/api/v2/assets/<asset_uid>/history
. You should get a 403.💭 Notes