Skip to content

v5.3.0

Choose a tag to compare

@placerda placerda released this 27 Oct 22:10
1ac69d8

Changed

  • Prepare all twelve architecture subnets by default for isolated deployments
    into new or existing VNets, including dedicated Power Platform and AI Gateway
    subnets with their service delegations.
  • Expose individual subnet creation switches and configurable names and IPv4
    ranges. Global subnet creation ownership applies consistently to both VNet
    paths; disabling creation does not disable a consuming service.
  • Separate application private endpoints from Foundry and grounding private
    endpoints by default. Use the reserved GatewaySubnet name without NSG,
    route-table or delegation attachments.
  • Validate consumer prerequisites, actual existing-network properties,
    overlapping ranges, delegated-subnet providers and APIM v2 integration NSG
    requirements before provisioning, without a shared-Foundry-subnet fallback.
  • These are defaults for new deployments. Occupied subnets and private endpoints
    are not automatically renamed or migrated; review explicit network inputs and
    resource dependencies before applying the changed topology.

Component versions

Component Version
agent-app-ui v3.3.1
agent-app-orchestrator v5.2.2
agent-app-ingestion v3.1.3
infra / AI Landing Zone v2.7.3

Validation

  • GitHub CI passes python -m pytest tests --quiet, Bicep build/lint and all
    17 offline foundation contract entrypoints. Subnet coverage includes 500
    assertions and exact mutation-tested preservation of historical fingerprints.
  • The deterministic preflight suite passes 382 assertions. Final targeted Python
    regression coverage passes 174 tests across resource groups, deployment modes,
    custom composition, provider prerequisites and regional quota checks.
  • Central documentation builds in strict MkDocs mode; all 36 subnet parameter
    bindings match the implementation.
  • Validation is offline; no live Azure provisioning was performed.