You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Today , we support providers with OpenAI compatible API and we differentiate them with types ( openai, rhelai_vllm etc) . We need a provider config which is very generic for any OpenAI compatible provider , and have the ability to specify the various authorization mechanisms . Recently, we observed a usage where the OpenAI compatible service with rotating tokens. But overall if we can provide a support for any OpenAI compatible provider, then we do not have to keep extending the types.
Describe the solution you'd like
Config needs to provide a support for any OpenAI compatible provider with its Authorization mechanism .
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Today , we support providers with OpenAI compatible API and we differentiate them with types ( openai, rhelai_vllm etc) . We need a provider config which is very generic for any OpenAI compatible provider , and have the ability to specify the various authorization mechanisms . Recently, we observed a usage where the OpenAI compatible service with rotating tokens. But overall if we can provide a support for any OpenAI compatible provider, then we do not have to keep extending the types.
Describe the solution you'd like
Config needs to provide a support for any OpenAI compatible provider with its Authorization mechanism .
The text was updated successfully, but these errors were encountered: