Is there a way to accommodate multiple endpoints and multiple keys for AzureOpenAI? Microsoft gave us different locations (EASTUS and EASTUS2) for our embedding model than our GPT-3 and GPT-4 access without the option to have all 3 models in one zone. This means that we have a different endpoint and key for the embedding model than our GPT-4 and GPT-3 model access. Is there a way to accommodate a different endpoint and key for each model in a webapi\.env file for docker compose? It would also be nice if this same thing were enabled for webapi\appsettings.json
Our current webapi\.env file looks like this (using fake values)...
Is there a way to accommodate multiple endpoints and multiple keys for AzureOpenAI? Microsoft gave us different locations (EASTUS and EASTUS2) for our embedding model than our GPT-3 and GPT-4 access without the option to have all 3 models in one zone. This means that we have a different endpoint and key for the embedding model than our GPT-4 and GPT-3 model access. Is there a way to accommodate a different endpoint and key for each model in a webapi\.env file for docker compose? It would also be nice if this same thing were enabled for webapi\appsettings.json
Our current webapi\.env file looks like this (using fake values)...
The request is that we would be able to specify different endpoints and keys like this (using fake values)...