-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support openai embeddings endpoints in ai proxy #1934
Support openai embeddings endpoints in ai proxy #1934
Conversation
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.
The router here still doesn't really make sense to me. Does it not direct /v1/embeddings to bedrock if that's the underlying provider? And same for the chat requests. We shouldn't be exposing bedrock url paths, it should just be the standard openai url paths.
…ndpoints-in-ai-proxy
@@ -153,7 +152,7 @@ func TestBedrockEmbeddingsProxy(t *testing.T) { | |||
{ | |||
Name: "embeddings request should return correct openai response", | |||
Method: "POST", | |||
Endpoint: bedrock.EndpointEmbeddings, | |||
Endpoint: "/v1/embeddings", |
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.
this needs to be on the same prefix as the other openai endpoints
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.
it's not?
console/go/ai-proxy/api/openai/openai.go
Line 18 in fb8f403
EndpointEmbeddings = "/v1/embeddings" |
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.
the other endpoints exposed were /openai/v1/chat/completions
. You can put it under both, but the openai path prefix is not a bad way to do it.
Test Plan
Checklist