fix: skip bucket seeding#5158
Open
7ttp wants to merge 2 commits intosupabase:developfrom
Open
Conversation
Coverage Report for CI Build 25209902879Coverage decreased (-0.01%) to 63.721%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions5 previously-covered lines in 1 file lost coverage.
Coverage Stats
💛 - Coveralls |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
skip local storage bucket seeding when no buckets are configured.
the unnecessary
GET /storage/v1/bucketcall was causingsupabase startto fail withError status 400: {"statusCode":"403","error":"Unauthorized","message":"new row violates row-level security policy"}sol:
buckets.Runnow returns early for local runs when[storage.buckets]is empty, configured local buckets and linked project bucket seeding still use the existing path unchangedadded a test aswell
ref:
supabase startfails with{"statusCode":"403","error":"Unauthorized","message":"new row violates row-level security policy"}#4866