azure.ai.agents - fix correlation ID propagation and tracing, update components to use azcore runtime.Pipeline by Copilot · Pull Request #6326 · Azure/azure-dev

Copilot · 2025-12-05T17:52:34Z

Refactors HTTP clients in the azure.ai.agents extension to use azcore.runtime.Pipeline instead of raw http.Client, enabling consistent policy handling, logging, and correlation headers across all HTTP requests.

Now the trace ID is properly propagated to the extension and being set in the X-Ms-Correlation-Request-Id header for outgoing API calls during azd ai agent init and agent deployment.

TODO

Rebase and uncomment main.go after Add distributed tracing and structured error handling for extensions #6321 is merged
Update go.mod and remove replace github.com/azure/azure-dev/cli/azd => ../..

Changes

Migrate to runtime.Pipeline

registry_api/operations.go - Replace http.Client with pipeline-based requests
foundry_projects_client.go - Same migration, plus fix for defer-in-loop resource leak

Add policies to ARM SDK clients

New client_options.go with NewArmClientOptions() helper providing standard policies
Updated all armcognitiveservices and armsubscriptions client instantiations in:
- init.go (ProjectsClient, DeploymentsClient)
- service_target_agent.go (ProjectsClient)
- model_catalog.go (ModelsClient)
- azure_client.go (subscriptions Client)

Debug logging in azd ai agent init

Support debug logging of HTTP requests and responses during azd ai agent init

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

code.cloudfoundry.org
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)
dario.cat
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)
go.googlesource.com
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)
go.opentelemetry.io
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)
go.uber.org
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)
go.yaml.in
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)
google.golang.org
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)
gopkg.in
- Triggering command: /update-job-proxy /update-job-proxy -o br-935d10f6676f -j DROP si_-_Surum_1.pem /opt/hostedtoolc-e /usr/bin/test 10 -buildtags /opt/hostedtoolc--global test -e igiCert_Assured_ID_Root_G2.pem /opt/hostedtoolc-e (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

This section details on the original issue you should resolve

<issue_title>azure.ai.agents - Update registry_api to use azcore runtime.Pipeline and policies</issue_title>
<issue_description>### Task 1
Update extension code in:

cli/azd/extensions/azure.ai.agents/internal/pkg/agents/registry_api/operations.go

cli/azd/extensions/azure.ai.agents/internal/pkg/azure/foundry_projects_client.go

other extension components that use direct HTTP requests (e.g., any usage of http.Client)

to use azcore's runtime.Pipeline for HTTP request handling. This is to enable policy, logging, and correlation header configuration similar to the agent_api/operations.go implementation. See #6137 as a reference.

Sub-tasks:

Refactor RegistryAgentManifestClient to use runtime.Pipeline and associated policies

Ensure credential, policy chaining, and diagnostic logging match agent_api usage

Review other components in azd/extensions/azure.ai.agents that perform direct HTTP requests (e.g., any usage of http.Client) and update them to use pipelines/policies as appropriate

Relevant files/components for review:

registry_api/operations.go (primary)

agent_api/operations.go (reference impl)

foundry_projects_client.go

Task 2

Update places where we create/use specific azure service clients from azure-sdk-for-go (e.g. armcognitiveservices.NewProjectsClient in cli/azd/extensions/azure.ai.agents/internal/cmd/init.go) to use similar policies and logging config as:
Logging: policy.LogOptions{
					AllowedHeaders: []string{azsdk.MsCorrelationIdHeader},
				},
				PerCallPolicies: []policy.Policy{
					azsdk.NewMsCorrelationPolicy(),
					azsdk.NewUserAgentPolicy(...),
				},
```</issue_description>

<agent_instructions>Use modern, idiomatic Go practices and if you see good opportunities for refactoring, please do so</agent_instructions>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

Fixes azure.ai.agents - Update registry_api to use azcore runtime.Pipeline and policies #6317

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

….Pipeline and add policies to ARM clients Co-authored-by: JeffreyCA <9157833+JeffreyCA@users.noreply.github.com>

Co-authored-by: JeffreyCA <9157833+JeffreyCA@users.noreply.github.com>

Copilot AI assigned Copilot and JeffreyCA Dec 5, 2025

Copilot started work on behalf of JeffreyCA December 5, 2025 17:52 View session

Copilot AI changed the title ~~[WIP] Update registry_api to use azcore runtime.Pipeline and policies~~ Update registry_api and foundry_projects_client to use azcore runtime.Pipeline Dec 5, 2025

Copilot AI requested a review from JeffreyCA December 5, 2025 18:14

Copilot finished work on behalf of JeffreyCA December 5, 2025 18:14

JeffreyCA changed the base branch from jeffreyca/ext-agents-operations to main December 5, 2025 18:15

JeffreyCA changed the title ~~Update registry_api and foundry_projects_client to use azcore runtime.Pipeline~~ azure.ai.agents - fix correlation ID propagation and tracing, update components to use azcore runtime.Pipeline Dec 5, 2025

JeffreyCA linked an issue Dec 5, 2025 that may be closed by this pull request

azure.ai.agents - support debug logging in azd ai agent init #6328

Closed

JeffreyCA and others added 8 commits December 12, 2025 00:40

Refactor agent API response handling to use runtime status code checks

819e737

Initial plan

c5bb9e9

Update registry_api and foundry_projects_client to use azcore runtime…

c181657

….Pipeline and add policies to ARM clients Co-authored-by: JeffreyCA <9157833+JeffreyCA@users.noreply.github.com>

Fix defer inside loop issue in GetAllConnections

cbedb55

Co-authored-by: JeffreyCA <9157833+JeffreyCA@users.noreply.github.com>

Support debug logging during init

2f80d8d

Add TODO to inject traceparent into context

28935b2

Refactor debug logging

4ff1be4

Update go.mod and go.sum after rebase

40cb7cb

JeffreyCA force-pushed the copilot/update-registry-api-pipeline branch from 9a39a1b to 40cb7cb Compare December 12, 2025 00:47

Update pipeline handling

ab7b25c

JeffreyCA marked this pull request as ready for review December 12, 2025 18:35

JeffreyCA requested review from hemarina, rajeshkamal5050, tg-msft, trangevi, vhvb1989, wbreza and weikanglim as code owners December 12, 2025 18:35

vhvb1989 approved these changes Dec 12, 2025

View reviewed changes

JeffreyCA merged commit ffa1a1e into main Dec 12, 2025
18 checks passed

JeffreyCA deleted the copilot/update-registry-api-pipeline branch December 12, 2025 22:38

This was referenced Dec 15, 2025

Create changelog for azure.ai.agents v0.1.4-preview #6379

Merged

Create changelog for v1.22.3 release #6381

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

azure.ai.agents - fix correlation ID propagation and tracing, update components to use azcore runtime.Pipeline#6326

azure.ai.agents - fix correlation ID propagation and tracing, update components to use azcore runtime.Pipeline#6326
JeffreyCA merged 9 commits into
mainfrom
copilot/update-registry-api-pipeline

Copilot AI commented Dec 5, 2025 •

edited by JeffreyCA

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

Copilot AI commented Dec 5, 2025 • edited by JeffreyCA Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

TODO

Changes

I tried to connect to the following addresses, but was blocked by firewall rules:

Task 2

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Dec 5, 2025 •

edited by JeffreyCA

Loading