-
Notifications
You must be signed in to change notification settings - Fork 274
feat: add passthrough_auth option for forwarding client Authorization header #687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you @tqtensor - this is a well thought out feature. Thanks for your contribution. We will take this change in. @adilhafeez will run the workflows for testing and perhaps offer a couple of small code review comments |
adilhafeez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only one minor comment - looks good overall. Thanks for your contribution @tqtensor
|
Created another PR to force run gh actions with api keys - #689 |
|
hey @tqtensor I just pushed a fix to your PR |
|
Thanks @salmanap and @adilhafeez for the quick review and help! I'm back online now and will check the updates. |
|
Btw @tqtensor would love for you to join our discord. Love contributions like these and hope to keep on building together |
Summary
This PR introduces the
passthrough_authoption for model providers, allowing Plano to forward the client'sAuthorizationheader directly to upstream LLM services or proxies.Changes
arch_config_schema.yamlto includepassthrough_auth(boolean).passthrough_authandaccess_keyare provided.commonandllm_gateway) to implement the header forwarding logic.supported_providers.rstexplaining the feature and use cases.config/test_passthrough.yaml.Verification Results
passthrough_authandaccess_keyare set.Closes #686