exp (iac): [foundry-deployment-agents] multi-version deployments and traffic routing#89
Draft
ferantivero wants to merge 2 commits intoAzure-Samples:mainfrom
Draft
Conversation
ferantivero
force-pushed
the
test/patch/538619_port-basic-website
branch
from
f71e2f1 to
7f4f72f
Compare
- add auto-suffix to deployment name (agentdeploychatv{version})
- add chat-with-bing-v2.json with concise response instructions
- update README with v1/v2 deployment and persist commands
Co-authored-by: GitHub Copilot (Claude Sonnet 4) <noreply@github.com>
- add optional step to route traffic to a specific deployment via trafficRoutingPolicy - document PUT with explicit deploymentId to control which deployment receives traffic - note control plane vs data plane separation (no jump box required) - document current limitations: no A/B split, no path/header routing, PUT required Co-authored-by: GitHub Copilot (Claude Sonnet 4) <noreply@github.com>
ferantivero
force-pushed
the
test/patch/538619_port-basic-website
branch
from
7f4f72f to
f99dded
Compare
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
1 participant
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
While working on agent publishing (#87), we wanted to experiment with multi-version agent deployments and understand how Foundry Agent Service handles traffic routing between them. The goal was to discover if and how we can control which agent version serves traffic from a single stable endpoint — useful for gradual rollouts and version management scenarios.
WHAT
agentVersionparameter with auto-suffix naming (agentdeploychatv{version})chat-with-bing-v2.json) with concise response instructionstrafficRoutingPolicywith explicitdeploymentId(control plane PUT)REVIEW
This PR includes commits from #87. Reviewers should focus on these two commits:
d558733— support multi-version agent deployments with auto-suffix naming7f4f72f— document traffic routing for multi-version agent deploymentsTEST
trafficRoutingPolicyPUT with explicitdeploymentIdDEPENDS ON
Co-authored-by: GitHub Copilot (Claude Sonnet 4) noreply@github.com