fix: use inline API key as BYOK fallback in AI Gateway#5614
Open
shouryamaanjain wants to merge 2 commits intoHelicone:mainfrom
Open
fix: use inline API key as BYOK fallback in AI Gateway#5614shouryamaanjain wants to merge 2 commits intoHelicone:mainfrom
shouryamaanjain wants to merge 2 commits intoHelicone:mainfrom
Conversation
…into env.js The supervisord environment directive was re-declaring env vars like NEXT_PUBLIC_HELICONE_JAWN_SERVICE and BETTER_AUTH_SECRET using %(ENV_...)s interpolation. This could override docker-compose values with Dockerfile defaults, preventing user-configured URLs from reaching the frontend. Fix: - Remove %(ENV_...)s re-declarations from supervisord.conf for both web and jawn programs — these vars are already set in the Dockerfile and are automatically inherited by child processes - Add docker-entrypoint.sh that generates __ENV.js from the container's actual NEXT_PUBLIC_* env vars before supervisord starts Closes Helicone#5551
When users provide their API key via the Authorization header but have no stored provider key in the database, the gateway now falls back to the inline key for BYOK routing instead of only using PTB (free-tier) keys. Closes Helicone#5561
|
@shouryamaanjain is attempting to deploy a commit to the Helicone Team on Vercel. A member of the Team first needs to authorize it. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
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.
Summary
Authorizationheader but have no stored provider key in the database, the gateway now falls back to the inline key for BYOK routing instead of only attempting PTB (free-tier) keys.Changes
inlineApiKeyparameter threaded throughbuildAttempts→buildAttemptsForAllProviders/getProviderAttempts→buildByokAttempts. When no stored BYOK key exists, creates a virtual provider key from the inline API key.inlineApiKey(only if it's not a Helicone auth key).Test plan
Closes #5561