Add hosted voice agent deployment support - #1
Conversation
Manual validation result (West US 2)Result: PASS
|
ab7cd25 to
5d06206
Compare
Private tester packageA Windows AMD64 private test share package is available locally:
SHA256:
Adjacent checksum file:
The package contains:
Validation completed:
|
Updated private test package — includes interactive init
SHA256:
Checksum file:
This replaces the previous package/checksum. It is built from PR head
Additional validation:
|
Final private test package — two standard azd scenarios
SHA256:
Built from PR head:
The test guide is intentionally reduced to the same two core scenarios used for Hosted Agent /
No TiP/ECS checks or manual project endpoint setup are required. Subscription, project, and model are selected in the normal init prompts. The package includes the original sample descriptor, source, runtime smoke tools, and results template. |
Final package retest — PASSRetested the final share package from a clean extraction and extension install. Package:
Final SHA256:
Private extension runtime:
Scenario 1 — Init from sample: PASS
Scenario 2 — Init into existing azd project: PASS
Notes:
|
Summary
modelType: hosted_agentandtargetAgent.serviceauthoring for Voice wrappersazd ai agent init -m agent.manifest.yamldirectly from the Hosted Voice sample descriptor--kind hosted-voice --no-promptfor CI automationSample experience
From the Hosted Voice sample directory:
The sample descriptor provides agent name, source, runtime, entry point, bundled dependency mode,
invocations_ws/1.0.0, and Voice Bridge metadata. The user only selects the subscription, Foundry project, and model deployment.Init generates:
voice-hosted-agent-dotnethosted targetvoice-hosted-agent-dotnet-voiceVoice wrapperRunning the same command from a sample subfolder inside an existing azd project appends both services to the existing root
azure.yamland preserves unrelated services.Validation
go test ./...go vet ./...init -mfrom the original .NET sample descriptor into a new projectinit -mfrom a sample subfolder into an existing valid azd project/helpthrough wrapper returned target-ownedCommands:responseFollow-up
azd downcleanup remains a follow-up.