openvidu/openvidu-deployment/pro/ha/azure
Piwccle fea2a9e9e8 openvidu-deployment: Azure HA — user-assigned identities so the Key Vault deploys first
Two user-assigned managed identities (master/media) replace the per-VM
system-assigned ones: the Key Vault's access policies now reference
principalIds known at deployment start, so the KV no longer depends on
the 4 VMs + VMSS existing and is created immediately in parallel
(removes the boot-time KV wait and its propagation window). Master
policy keeps get/set/list, media keeps get, deploymentUser untouched.
Role assignments consolidated 5 -> 2 and repointed to the identities
(principalType ServicePrincipal). All 10 az login calls use
--client-id; azure-cli pinned 2.87.0 -> 2.88.0 (verified available in
the Microsoft apt repo for noble). No public parameters/outputs change.

Validated with ov-cloud-tester (sc-deploy-destroy, ha, dev): PASS.
deploy 2m9s, wait-ready 7m48s, destroy 8m20s.
2026-07-29 11:56:08 +02:00
..
DOC-CHANGES-ha-optimizations.md openvidu-deployment: Azure HA — user-assigned identities so the Key Vault deploys first 2026-07-29 11:56:08 +02:00
cf-openvidu-ha.bicep openvidu-deployment: Azure HA — user-assigned identities so the Key Vault deploys first 2026-07-29 11:56:08 +02:00
cf-openvidu-ha.json openvidu-deployment: Azure HA — user-assigned identities so the Key Vault deploys first 2026-07-29 11:56:08 +02:00
createUiDefinition.json openvidu-deployment: optimize Azure HA deployment time 2026-07-24 14:31:46 +02:00