feat(agents): resolve Foundry project from endpoint so deploy runs without provision#8638
Merged
huimiu merged 1 commit intoJun 15, 2026
Conversation
Member
Author
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.
What
Stacks on #8629. Adds endpoint-based Foundry project resolution so
azd deploycan target an existing Foundry project viaendpoint:withoutazd provision(design spec #8590 §1.4).Today the
microsoft.foundrydeploy path resolves the target resource through the sharedGetTargetResource->ensureFoundryProject, which hard-requiresAZURE_AI_PROJECT_ID(an ARM id normally written by provision). With onlyendpoint:set, deploy fails before any data-plane call. This unblocks the minimal end-to-end demo against an existing project.Changes
internal/project/foundry_project_resolve.go(new):parseFoundryEndpoint- parse account/project fromhttps://<account>.services.ai.azure.com/api/projects/<project>.resolveFoundryProjectIDFromEndpoint- list Foundry projects in the subscription, match account+project, return the ARM resource id.FoundryServiceTargetProvider.resolveProjectFromEndpoint- whenAZURE_AI_PROJECT_IDis absent and an endpoint is available (serviceendpoint:with${VAR}expansion, orFOUNDRY_PROJECT_ENDPOINT), resolve and persistAZURE_AI_PROJECT_ID.internal/project/service_target_foundry.go-InitializecallsresolveProjectFromEndpointafter auth setup.internal/project/foundry_project_resolve_test.go(new) - table-drivenparseFoundryEndpointcoverage.Provisioned projects are unaffected: resolution is skipped when
AZURE_AI_PROJECT_IDalready exists.Out of scope (follow-ups toward the minimal demo)
initrework (one-file azure.yaml), data-plane reconcile (deployments/connections/...), built-in Bicep provision,$refwiring, multi-agent fan-out.Testing
Extension module:
go build ./...,go vet,go test ./internal/project/...,golangci-lint run(0 issues),gofmt,cspell- all clean.