-
Notifications
You must be signed in to change notification settings - Fork 888
Feat/databricks provider #1505
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
base: main
Are you sure you want to change the base?
Feat/databricks provider #1505
Conversation
- Add support for Databricks AI Gateway as a Portkey provider - Implements chat completions, text completions, and embeddings - Uses unified /invocations endpoint for all operations - Maintains OpenAI-compatible request/response format - Supports workspace-based and custom base URLs - Bearer token authentication with Databricks PATs - Tested with Meta Llama, Anthropic Claude, and embedding models
…into feat/databricks-provider
| export const IO_INTELLIGENCE: string = 'iointelligence'; | ||
| export const AIBADGR: string = 'aibadgr'; | ||
| export const OVHCLOUD: string = 'ovhcloud'; | ||
| export const DATABRICKS_AI: string = 'databricks-ai'; |
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.
I registered the provider as 'databricks' in providers/index.ts. I have a relatively strong preference that the provider identifier be just 'databricks' to match the pattern of other major providers like 'openai', 'anthropic', etc. Can we keep it as 'databricks' instead of 'databricks-ai'?
|
Hello @b4s36t4 and @narengogi , thanks so much for your reviews! |
|
Hi all, following up on the above. Anything I can do to expedite the review? |
Description: (required)
Tests Run/Test cases added: (required)
Type of Change: