You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
Fix Terraform provisioning failing with useUAI requires a native bool value when optional azd settings such as USE_UAI, NETWORK_ISOLATION, ENABLE_AGENTIC_RETRIEVAL, USE_EXISTING_VNET, SIDE_BY_SIDE or EXISTING_VNET_RESOURCE_ID are unset. Unset placeholders without a default are now omitted so Terraform applies its declared defaults, matching how azd omits empty Bicep parameters. Explicit empty values are still rejected for typed inputs. Bicep is unaffected.
Migration: no action required. Rollback: restore v7.5.0 and set every affected variable explicitly before provisioning with Terraform. Runtime component pins and infrastructure provenance are unchanged.
Component versions
Component
Version
agent-app-mcp
v2.0.0
agent-app-ui
v3.7.0
agent-app-orchestrator
v7.2.0
agent-app-ingestion
v3.1.3
infra / AI Landing Zone
v2.7.3
Validation
Feature CI run 43617187557 and release CI passed Bicep build and lint, Terraform contracts on Linux and Windows and deployment and hook contracts on Linux and Windows, including new regression tests for unset and explicitly empty inputs.
python -m pytest tests/test_release_contracts.py passed 17 tests and 6 subtests.
The defect was found by a live Terraform deployment of v7.5.0 with NETWORK_ISOLATION=true in a validation environment, which failed in preprovision.