As Zhenlan Wang (@zhenlan) has describe below, the App Configuration pipeline tasks currently don't have built-in support for replica discovery and failover. Please add this support natively to the ADO task so that each pipeline does not have to manually parameterize and manage their own list of replicas.
Edited. Original title and question below.
How Is DR/Failover/Automatic Replica Discovery Configured with the Azure DevOps Extensions?
If all my Azure Pipelines read config from the ADO task AzureAppConfiguration@8 and they point to an Azure App config resource in South Central US, if the entire South Central US region is down, how should I have AzureAppConfiguration@8 configured so that it fails over to one of my many geo-replicas?
As Zhenlan Wang (@zhenlan) has describe below, the App Configuration pipeline tasks currently don't have built-in support for replica discovery and failover. Please add this support natively to the ADO task so that each pipeline does not have to manually parameterize and manage their own list of replicas.
Edited. Original title and question below.
How Is DR/Failover/Automatic Replica Discovery Configured with the Azure DevOps Extensions?
If all my Azure Pipelines read config from the ADO task AzureAppConfiguration@8 and they point to an Azure App config resource in South Central US, if the entire South Central US region is down, how should I have AzureAppConfiguration@8 configured so that it fails over to one of my many geo-replicas?