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
After completing deployment I can see the endpoint on AI Studio. Following the instructions in the README I proceed to test it with the following input:
{"question": "Tell me about hiking shoes", "customerId": "2", "chat_history": []}
The above produces an error, however, triggered during the instantiation of the AzureOpenAIModelConfiguration object. As seen in the logs:
"Execution failure in 'get_response': (InvalidConnectionError) AzureOpenAIModel parameters are incomplete. Please ensure azure_endpoint, api_version, and api_key are provided."
Although we do explicitly provide the version and endpoint here, we don't do the same for the API key. In fact, inspecting my local azd env, the value of AZURE_OPENAI_API_KEY is not set. This feels like something that should be part of the postprovision script. Diving deeper, I noticed that a relevant looking key (is it the same one?) used to be set among others here prior to the May 2024 updates. Why was this dropped?
I'm currently using the following package versions:
After completing deployment I can see the endpoint on AI Studio. Following the instructions in the README I proceed to test it with the following input:
The above produces an error, however, triggered during the instantiation of the
AzureOpenAIModelConfiguration
object. As seen in the logs:Although we do explicitly provide the version and endpoint here, we don't do the same for the API key. In fact, inspecting my local
azd env
, the value ofAZURE_OPENAI_API_KEY
is not set. This feels like something that should be part of the postprovision script. Diving deeper, I noticed that a relevant looking key (is it the same one?) used to be set among others here prior to the May 2024 updates. Why was this dropped?I'm currently using the following package versions:
The text was updated successfully, but these errors were encountered: