Skip to content

Python: Switch to using new azure.yaml templates for azd deployments - #10391

Open
Darren Cohen (dargilco) wants to merge 3 commits into
python-foundry-hosting-rcfrom
dargilco/use-new-azure-yaml
Open

Darren Cohen (dargilco) wants to merge 3 commits into
python-foundry-hosting-rcfrom
dargilco/use-new-azure-yaml

Conversation

@dargilco

@dargilco Darren Cohen (dargilco) commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Motivation & Context

Python Foundry hosted-agent samples still used the legacy agent.manifest.yaml and agent.yaml pair with azd ai agent init -m. The current azd workflow uses a single azure.yaml template and the -t option. Updating the samples and their guidance keeps initialization and deployment instructions aligned with that workflow.

Description & Review Guide

  • What are the major changes? Migrated the legacy hosted-agent sample projects to individual azure.yaml files, updated Telegram's existing configuration, and removed the obsolete manifests. Updated shared and sample-specific READMEs and the hosted-agent validation guidance. Updated the Toolbox samples' ignore rules and made Hyperlight's Docker build self-contained.
  • What is the impact of these changes? The samples use azd ai agent init -t and define their own service/deployment configuration. Local schema and configuration checks passed. A pre-existing Telegram executable-bit assertion was excluded on Windows; authenticated deployment and Docker image builds were not verified.
  • What do you want reviewers to focus on? Confirm each sample's azure.yaml preserves its specific agent, model, connection, and deployment requirements; that the Toolbox template inputs are retained without copying secrets into images; and that the README and validation guidance match the new initialization flow.

Related Issue

Closes #7250

AI Assistance

  • No material AI assistance was used.
  • This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: Copilot assisted with the implementation, tests, documentation, and this PR description.

Contribution Checklist

  • The code builds clean without any errors or warnings
  • All unit tests pass, and I have added new tests where possible
  • The PR follows the Contribution Guidelines
  • This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
  • This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

@agent-framework-automation agent-framework-automation Bot added documentation Usage: [Issues, PRs], Target: documentation in the code base and learn docs python Usage: [Issues, PRs], Target: Python labels Nov 16, 2026
@github-actions github-actions Bot changed the title Switch to using new azure.yaml templates for azd deployments Python: Switch to using new azure.yaml templates for azd deployments Nov 16, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MAF Automated Review — Iteration 1

Result: No findings
Scope: full PR (1 commit(s)): f545873f93be
Model: gpt-5.6-sol

Overview

This PR replaces split hosted-agent manifests with self-contained azure.yaml projects and adds broad structural tests across all migrated samples. The tests cover project/agent topology, protocols, entry points, model and sample-specific environment wiring, managed Toolbox dependencies, and deployment ignore rules. The raised schema concerns are contradicted by the canonical template contract, and the credential-backed Toolbox policy predates this change, so no publishable PR-introduced defect remains.

Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
No publishable findings remained after source verification for this scope.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
from agent_framework.foundry import FoundryChatClient, FoundryChatOptions, ResponsesHostServer
from agent_framework.foundry import FoundryChatClient, FoundryChatOptions
from agent_framework.hyperlight import HyperlightCodeActProvider
from agent_framework_foundry_hosting import ResponsesHostServer

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this shouldn't change, we want to use the .foundry namespace when available.

This branch was successfully deployed

1 active deployment
github-app-auth — b3398197 Deployed Nov 16, 2026 by dargilco via add_label #27927
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Usage: [Issues, PRs], Target: documentation in the code base and learn docs python Usage: [Issues, PRs], Target: Python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants