Repository navigation
Python: Switch to using new azure.yaml templates for azd deployments - #10391
Darren Cohen (dargilco) wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
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>
Motivation & Context
Python Foundry hosted-agent samples still used the legacy
agent.manifest.yamlandagent.yamlpair withazd ai agent init -m. The current azd workflow uses a singleazure.yamltemplate and the-toption. Updating the samples and their guidance keeps initialization and deployment instructions aligned with that workflow.Description & Review Guide
azure.yamlfiles, 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.azd ai agent init -tand 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.azure.yamlpreserves 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
AI assistance details: Copilot assisted with the implementation, tests, documentation, and this PR description.
Contribution Checklist
breaking changelabel (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.