fix: detect deployed agent invoke protocol - #9808
Conversation
|
Azure Pipelines: Successfully started running 3 pipeline(s). 24 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
3887d3b to
2933985
Compare
azure.ai.agents PR buildNote This is an unsigned development build. Install it only if you trust this PR. Install the extension: azd ext install "https://azuresdkartifacts.z5.web.core.windows.net/azd/extensions/pr/9808/azure-ai-agents.zip"
|
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
Why this is needed
Remote
azd ai agent invokepreviously relied on the local agent definition to choose a protocol. When that definition was stale or missing, a deployedinvocationsagent could receive aresponsespayload and fail with an invalid-payload error.Approach
Remote protocol selection now reads the deployed agent endpoint configuration, filters to invocable protocols, and uses the local definition only when multiple deployed protocols need disambiguation. Explicit protocol and endpoint choices remain authoritative, local invocation behavior is unchanged, and the resolved remote context is reused for the request. Conversation handling was not changed.
Testing
go test ./...incli/azd/extensions/azure.ai.agentsFixes: #7507