fix(cli): allow local storage without access token#5587
Closed
avallete wants to merge 1 commit into
Closed
Conversation
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@586334efcfc71fce5b16a2a1f2ca29a8d5643c27Preview package for commit |
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.
What kind of change does this PR introduce?
Bug fix.
What is the current behavior?
supabase storage --localfails before reaching the storage handler when noSUPABASE_ACCESS_TOKENis configured. The storage command is grouped with Management API commands, so the shared root pre-run prompts for login before the local Storage API client can be selected.Closes #3455.
What is the new behavior?
Local storage subcommands bypass the Management API login gate when storage is explicitly targeting the local stack. Default and linked storage usage still requires an access token.
The PR also adds command-level coverage for the linked/default storage auth path and the explicit local storage bypass.
Additional context
This is separate from the TypeScript typegen port regression discussed in #5551. Storage is still handled by the legacy Go command path; the TypeScript shim forwards
--local, and the auth failure happens in the Go root pre-run.