Add configurable upstream auth header handling#2
Open
jeeftor wants to merge 1 commit into
Open
Conversation
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.
Summary
This adds per-model upstream auth configuration so backends can receive a configured
api_keyeither as:Authorization: Bearer <api_key><custom-header>: <api_key>The default behavior remains unchanged for existing configs:
Authorization: Bearerx-api-keywith a raw key valueConfig examples
Default bearer auth:
Explicit bearer auth:
Raw custom-header auth:
Changes
auth_header_nameandauth_schememodel config fieldsauth_schemevaluesbearerandrawconfig.yaml.exampleanddocs/config-reference.mdWhy
Some OpenAI-compatible backends expect API keys in a non-default header instead of
Authorization: Bearer .... This change makes that configurable without duplicating secrets into arbitrary extra headers.Backward compatibility
Existing configs continue to work unchanged.
Testing
go test ./internal/config ./internal/handlergo test ./internal/pipeline -run 'TestDescribeImage|TestProcessImage|TestDescribeImage_FallsBackToReasoningContent'The broader
internal/pipelinepackage still has unrelated environment-dependent PDF test failures.Closes #1