archive/blender-cloud
0
1
Fork 1
Code Issues 24 Pull Requests Packages Projects Releases Wiki Activity

Deleting an account should be possible #71361

New Issue
Open
opened 2019-11-05 14:21:51 +01:00 by Sybren A. Stüvel · 1 comment
Sybren A. Stüvel commented 2019-11-05 14:21:51 +01:00
Copy Link

Currently it's not possible to delete someone's account on Blender Cloud without hacking the database directly. For obvious reasons this is not a good approach.

Account deletion could be implemented in a few incremental steps:

  • Allow an admin to anonymise a user document. This would remove the email address, change the name and other identifying information to '[account deleted]', set some flag to indicate deletedness (probably {'_deleted': true}, and remove authentication information. By anonymising the user document (and not deleting it) we don't have to worry about other parts of Blender Cloud crashing because it receives None instead of a user. Note that this change should also trigger a re-index of the user in ElasticSearch.
  • Create a periodical cleanup task to handle orphaned data.
    • Delete files and nodes owned by deleted users or reassign them to still-existing project members.
    • Delete projects owned by deleted users, or reassign them to still-existing project members.
    • Same for Flamenco Managers, jobs, tasks, etc.
  • Allow a user to request the above to happen.
  • Listen to deletion requests from Blender ID.
Currently it's not possible to delete someone's account on Blender Cloud without hacking the database directly. For obvious reasons this is not a good approach. Account deletion could be implemented in a few incremental steps: - Allow an admin to anonymise a user document. This would remove the email address, change the name and other identifying information to '[account deleted]', set some flag to indicate deletedness (probably `{'_deleted': true}`, and remove authentication information. By anonymising the user document (and not deleting it) we don't have to worry about other parts of Blender Cloud crashing because it receives `None` instead of a user. Note that this change should also trigger a re-index of the user in ElasticSearch. - Create a periodical cleanup task to handle orphaned data. - Delete files and nodes owned by deleted users or reassign them to still-existing project members. - Delete projects owned by deleted users, or reassign them to still-existing project members. - Same for Flamenco Managers, jobs, tasks, etc. - Allow a user to request the above to happen. - Listen to deletion requests from Blender ID.
Sybren A. Stüvel commented 2019-11-05 14:21:51 +01:00
Author
Copy Link

Added subscribers: @dr.sybren, @fsiddi, @SemMulder

Added subscribers: @dr.sybren, @fsiddi, @SemMulder
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: Websites
legacy project
Infrastructure: blender.org
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
No Label
Priority::High
Status::Confirmed
Type::Design
legacy project
Blender Cloud
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
blender-admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archive/blender-cloud#71361
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?