feat: support declaring objects path for seeding buckets #2591
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.
What kind of change does this PR introduce?
feature
What is the new behavior?
Allows configuring an
objects_path
for seeding buckets. Files under the path will be uploaded to their respective bucket.Path will be resolved relative to
config.toml
, ie. the path above resolves tosupabase/images
.Also seeds automatically when running the following commands locally
supabase start
supabase db reset
For hosted projects, a separate command needs to be run:
supabase seed buckets
Additional context
This works fine for small objects but large files will require a separate solution.