FlowiseAI/Flowise

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

Open

#960 opened on Sep 22, 2023

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

Description

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

Contributor guide

Tech stack
typescriptreactnodejsazure
Domain
backendcloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of Azure OpenAI endpointsFamiliarity with Flowise codebase structureTypeScript knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.