-
Notifications
You must be signed in to change notification settings - Fork 846
Open
Labels
Description
What Would You Like to See with the Gateway?
currently if users want to send arbitrary payloads through the gateway to different endpoints not supported by the gateway, they have to use openai (or one of the supported providers) as the base provider and add the path parameters in the url, alongwith the x-portkey-custom-host header
example #1
this is how you'd call an arbitrary endpoint for milvus (supported provider)
curl --location 'http://localhost/v1/v2/vectordb/collections/list' \
--header 'x-portkey-custom-host: https://in03-34d72c7.serverless.gcp-us-west1.cloud.zilliz.com' \
--header 'Authorization: Bearer asd' \
--header 'x-portkey-provider: milvus'for an unsupported provider, you'd use openai as the provider (you can add custom headers with x-portkey-forward-headers
so the same would look like this
curl --location 'http://localhost/v1/v2/vectordb/collections/list' \
--header 'x-portkey-custom-host: https://in03-34d72c7.serverless.gcp-us-west1.cloud.zilliz.com' \
--header 'Authorization: Bearer asd' \
--header 'x-portkey-provider: openai'Context for your Request
No response
Your Twitter/LinkedIn
No response