feat(cli): expose SUPABASE_PUBLISHABLE_KEY in branches get env output#5655
Open
mittal-parth wants to merge 1 commit into
Open
feat(cli): expose SUPABASE_PUBLISHABLE_KEY in branches get env output#5655mittal-parth wants to merge 1 commit into
mittal-parth wants to merge 1 commit into
Conversation
branches get -o env|json mapped API keys to SUPABASE_<NAME>_KEY by name only. New-format publishable and secret keys both use name default, so the secret overwrote the publishable and SUPABASE_PUBLISHABLE_KEY was never emitted. This change maps publishable keys named default to SUPABASE_PUBLISHABLE_KEY in the shared ToEnv helper so branches get and projects api-keys return the client key for preview env injection.
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
1 participant
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 is the current behavior?
branches get -o env|jsonmapped API keys toSUPABASE_<NAME>_KEYby name only. New-format publishable and secret keys both use namedefault, so the secret overwrote thepublishableandSUPABASE_PUBLISHABLE_KEYwas never emitted.What is the new behavior?
This change maps publishable keys named default to
SUPABASE_PUBLISHABLE_KEYin the sharedToEnvhelper sobranches getandprojects api-keysreturn the client key for preview env injection.Additional context
Closes #5654