Managing redaction of users #128
Labels
No labels
automation
backend
bug
contributor experience
data
deployment
documentation
duplicate
good first issue
help wanted
nice to have
notifications
package maintainer
performance
skin
tech debt
user story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-community/nix-security-tracker#128
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Check the management of user deletion with regards to activity logs.
We'll need to decide on what to do when a user asks to be deleted from the database in order to not to lose the overall overview of changes.
Context: https://github.com/Nix-Security-WG/nix-security-tracker/pull/126#pullrequestreview-1781939821 and https://github.com/Nix-Security-WG/nix-security-tracker/pull/126#issuecomment-1856283951
Since #366 has landed, this issue can be closed. The way
pghistory
keeps the user that made a certain action is to register its user ID inpgh_context
.I did try locally making actions and deleting users from the database, and the activity log is keeping the actions. In this case, the UI logic identifies that an ID pointing to a non-existent user means the user has been redacted, and is displayed as such.