feat(projectHistoryLogs): project history logs for bulk actions TASK-1229

[Guitlle]

🗒️ Checklist

1. run linter locally
2. update all related docs (API, README, inline, etc.), if any
3. draft PR with a title <type>(<scope>)<!>: <title> TASK-1234
4. tag PR: at least frontend or backend unless it's global
5. fill in the template below and delete template comments
6. review thyself: read the diff and repro the preview as written
7. open PR & confirm that CI passes
8. request reviewers, if needed
9. delete this section before merging

📖 Description

This PR adds support for bulk actions logging.

👀 Preview steps

1. Create two new projects
2. Deploy the projects
3. Execute the bulk actions for the 2 projects (archive, unarchive, delete and undelete) (NOTE: the frontend currently doesn't allow me to do bulk archive/unarchive actions, only delete)
4. To test the archive and unarchive, the UI may not allow you to perform these actions, however you can use curl:

$ curl -X POST -H "Authorization: Token xxx" -d "{\"payload\": {\"action\": \"unarchive\", \"asset_uids\": [\"ae6hQt9s2phfjRnsNphLdA\", \"auYiwftdP2g8axKkiUB8cE\"]}}" -H "Content-Type: application/json"  http://kf.kobo.local/api/v2/assets/bulk/ 

{"detail":"2 projects have been unarchived"}

$ curl -X POST -H "Authorization: Token xxx" -d "{\"payload\": {\"action\": \"archive\", \"asset_uids\": [\"ae6hQt9s2phfjRnsNphLdA\", \"auYiwftdP2g8axKkiUB8cE\"]}}" -H "Content-Type: application/json"  http://kf.kobo.local/api/v2/assets/bulk/ 

{"detail":"2 projects have been archived"}

$ curl -X POST -H "Authorization: Token xxx" -d "{\"payload\": {\"action\": \"undelete\", \"asset_uids\": [\"aUxHmB9wAqr5yVtZeW3sdc\", \"aqTWH6Wkv9wMbUL3PeLR44\"]}}" -H "Content-Type: application/json"  http://kf.kobo.local/api/v2/assets/bulk/

{"detail":"2 projects have been undeleted"}      

5. Check the logs were created through the django shell

$ ./run.py -cf exec kpi bash 
$ ./manage.py shell_plus
...
In[]: us = User.objects.get(username="super_admin")
In[]:  for log in ProjectHistoryLog.objects.filter(user=us).order_by('-date_created')[0:8]: print(log.date_created, log.action, log.metadata['asset_uid'])

2024-11-14 23:50:19.482422+00:00 archive auYiwftdP2g8axKkiUB8cE
2024-11-14 23:50:19.468558+00:00 archive ae6hQt9s2phfjRnsNphLdA
2024-11-14 23:50:03.891367+00:00 unarchive auYiwftdP2g8axKkiUB8cE
2024-11-14 23:50:03.848762+00:00 unarchive ae6hQt9s2phfjRnsNphLdA
2024-11-14 18:36:23.187022+00:00 archive ae6hQt9s2phfjRnsNphLdA
2024-11-14 18:32:28.181161+00:00 delete aUxHmB9wAqr5yVtZeW3sdc
2024-11-14 18:32:27.498762+00:00 delete aqTWH6Wkv9wMbUL3PeLR44
...

💭 Notes

[rgraber]

Two things:

1. It was super not-obvious on the task (sorry) but we only need to worry about bulk archiving and non-archiving.
2. Can we stick with the pattern of adding things to the request, then going through ProjectHistoryLog.create_from_request? It is easier to reason about if the code all generally flows through one place

[rgraber]

why did this change?

[Guitlle]

this was a complain from the linter :S ... probably from some merge, that is not related to this PR

[rgraber]

we shouldn't create the logs until after we've completed the actions. if something fails, we don't want a log saying it succeeded.

[Guitlle]

If we put the logs creation in the middleware, it will run before the rest of the request processing. So I am wondering if we can detect if it's going to fail or maybe have a hook that runs after the successful response is created

[Guitlle]

Nevermind, I'm checking the middleware code and it should run after the action was executed.