2
`deleteUser()`: Add option to delete user-owned files
Source: supabase/supabase#15424 · opened by @imageck
Currently, if a user owns any object in the storage, their account is not allowed to be deleted. The way to do it right now is by using triggers, cron jobs and such. This is not a trivial task, nor is it seamless.
Ideally, deleteUser() should accept an option akin to shouldSoftDelete, perhaps even named similarly, e.g. shouldHardDelete. From there on, there is a couple of options:
1. Start the deletion process asynchronously, then return the status.
2. Clear the owner column from storage.objects, marking those files for deletion at a later point, e.g. by a cron job.
Ideally, deleteUser() should accept an option akin to shouldSoftDelete, perhaps even named similarly, e.g. shouldHardDelete. From there on, there is a couple of options:
1. Start the deletion process asynchronously, then return the status.
2. Clear the owner column from storage.objects, marking those files for deletion at a later point, e.g. by a cron job.
No pledges yet. Be the first to back this.
Comments
Similar requests
Move `deleteUser()` to client
3 votes · 0 comments
Accept `auth` options passed to `createPagesServerClient`
1 vote · 0 comments
Creating tables related to bucket files (demo + idea)
1 vote · 0 comments
[storage-js] Skip `.from('bucket')` storage calls syntax for `createSignedUrls` function
1 vote · 0 comments
Dashboard Enhancement: Add Edit and Delete actions for Database Views
3 votes · 0 comments
No comments yet.