Change a file's owner in storage.objects
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- postgresql, typescript
- Domain
- authorization, backend, databases
Research direction
Start with the SupabaseClient and storage.objects references in the issue, then review storage-api issue #65 to understand the existing ownership cleanup behavior. Define the admin or server-side transfer behavior and verify that ownership changes to the selected user without weakening access controls.
Written by the indexing model from the issue text.
Description
I've been searching for a way to change the owner of a file in storage.objects from the SupabaseClient and can't find a way. The closest solution I found was to make it null after the user is deleted (via https://github.com/supabase/storage-api/issues/65).
I would like the ability for an admin user to change / transfer the ownership of a file to another user, or handle that operation pn the server.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 307
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 44
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/storage
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 75/100
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in supabase/storage
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·