Draft
feat(azure.ai.agents): add invocations_ws (WebSocket) protocol support#9193
Conversation
|
Azure Pipelines: 20 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: v1212 <49907914+v1212@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix code based on review comment in PR #9009
feat(azure.ai.agents): add invocations_ws (WebSocket) protocol support
Jul 17, 2026
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.
Adds
invocations_wsas a supported protocol in theazure.ai.agentsextension, and refactors the protocol resolution path to eliminate a redundantprotocolInfo→ProtocolVersionRecordconversion.Core changes
init_from_code.go: Addsinvocations_ws(2.0.0) toknownProtocols; extractsresolveKnownProtocols()returning[]agent_yaml.ProtocolVersionRecorddirectly so callers no longer need a conversion loop;promptProtocolsdelegates its flag-path toresolveKnownProtocolsinit.go: AddsprotocolRecordsForImageManifest()for the--imageflow with an explicit rejection ofactivity(which is only valid for code-deploy init); updatessynthesizeImageManifestFileto acceptflagProtocols; updates--protocolhelp texthosted-agent-regions.json: Addswestus2schemas/azure.ai.agent.json: Addsinvocations_wstoProtocolVersionRecord.protocoldescriptionTests
TestKnownProtocolNames— assertsinvocations_wsis listedTestPromptProtocols_FlagValues/invocations_ws_only— flag path resolves correct versionTestPromptProtocols_Interactive/websocket_protocol_selected— interactive selection worksTestPromptProtocols_ChoicesIncludeInvocationsWsWithoutChangingDefault—invocations_wsappears in choices but default remainsresponsesTestSynthesizeImageManifestFile_{UsesFlagProtocols,RejectsUnknownProtocol,RejectsActivityProtocol}TestCreateAgentAPIRequest_CodeDeploy_InvocationsWsUsesProtocolVersions