fix: detect deployed agent invoke protocol - #9808
Draft
Hui Miao (huimiu) wants to merge 1 commit into
Draft
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. |
Contributor
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"
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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