FlowiseAI/Flowise

[FEATURE] need more freedom to input post url for AZURE

Open

#960 opened on 2023年9月22日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)TypeScript (52,823 stars) (24,335 forks)batch import
enhancementhelp wanted

説明

Describe the feature you'd like

currently the Azure wrapper assumes that the endpoint follows this format :

https://{your-resource-name}.openai.azure.com/openai/deployments/{deployment-id}/chat/completions?api-version={api-version}

but it could be that the endpoint follows this format :

https://eastus2.api.cognitive.microsoft.com/

especially for the 32K preview/private open ai model(s)

you it would be nice to have control over the base url , actually the whole url, and maybe point the user to the playground where they can copy their entire url

Additional context image

コントリビューターガイド

技術スタック
typescriptreactnodejsazure
領域
backendcloud
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Basic understanding of Azure OpenAI endpointsFamiliarity with Flowise codebase structureTypeScript knowledge
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
Start by examining the current Azure OpenAI integration code in the Flowise repository, likely in a file related to Azure credentials or chat models. The issue requests allowing users to input a custom base URL instead of the hardcoded format. Look for the function that constructs the endpoint URL and consider adding a configuration option for the full URL. The existing comments or linked PRs may provide hints. Check the Flowise documentation or code comments for guidance on the expected changes. Ensure backward compatibility with existing deployments.