Say I’m deploying a 12 Factor app in Azure and I’m storing all my configuration for said application in Azure App Configuration Service (AACS). In order to ensure proper isolation between stages, I’m hosting dev, integ, staging, and prod all in their own subscriptions, which means I’ll have an AACS instance in each subscription with the environment config for that stage.
This is all great, until you realize that you’ve got a chicken and egg problem. Because AACS requires a unique name for each instance, and by 12 factor principles, you shouldn’t code configuration into the code, we’ve got a bootstrapping/discovery problem for your app to find the AACS instance.
How do you all handle this issue?