fix(cli): inject S3 and sb key env variables into Studio#5438
Merged
Conversation
Coverage Report for CI Build 26883280758Warning No base build found for commit Coverage: 63.922%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
Coly010
approved these changes
Jun 3, 2026
aantti
approved these changes
Jun 3, 2026
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
4 participants
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 changed
This wires Studio with the local S3 protocol credentials and the newer opaque Supabase key environment variables in both the Go CLI stack and the TypeScript stack implementation.
The change keeps the existing legacy Studio key variables intact while adding
SUPABASE_PUBLISHABLE_KEY,SUPABASE_SECRET_KEY,S3_PROTOCOL_ACCESS_KEY_ID, andS3_PROTOCOL_ACCESS_KEY_SECRET.Why
Studio expects these values for local S3 key access and newer key handling, but the CLI-managed Studio container only received the legacy key variables before this change.