App Configuration Management
Synopsis​
Intended end result: Keep non-secret CONDOR deployment configuration synchronized between local parameters and Azure App Configuration.
How this page gets you there: Use the publish script to push non-sensitive parameters from parameters.bicepparam into App Configuration, then validate keys and labels after publish.
Use this page for non-secret configuration values (naming, feature flags, endpoints, sizing, and runtime settings).
For sensitive values (passwords, PATs, API keys, and tokens), use Deployment Parameter Secret Management instead.
Target App Configuration store:
- Name: azw2-appcs-wfca-alertca-hub-001
- Subscription: a8e28801-b3eb-445c-87f6-ac9f0470aa86
- Key prefix convention: Condor:*
Publish non-secret configuration to App Configuration​
Preview what would be published (no Azure write):
cd azure\infrastructure
.\scripts\publish-AICondorDeploymentConfigToAppConfig.ps1 -DryRun
Publish only changed/new values (default, recommended):
cd azure\infrastructure
.\scripts\publish-AICondorDeploymentConfigToAppConfig.ps1
Publish all mapped keys (force overwrite mode):
cd azure\infrastructure
.\scripts\publish-AICondorDeploymentConfigToAppConfig.ps1 -ForceAll
Publish with an explicit label (for environment scoping):
cd azure\infrastructure
.\scripts\publish-AICondorDeploymentConfigToAppConfig.ps1 -Label uat
Verify published keys​
List Condor keys with null label:
az appconfig kv list --name azw2-appcs-wfca-alertca-hub-001 --key "Condor:*" --label "\0" -o table
List Condor keys for label uat:
az appconfig kv list --name azw2-appcs-wfca-alertca-hub-001 --key "Condor:*" --label uat -o table
Check a specific key value:
az appconfig kv show --name azw2-appcs-wfca-alertca-hub-001 --key "Condor:FrontDoor:WafPolicyName" --label "\0" -o json
How restore uses App Configuration​
The restore workflow merges App Configuration (non-secret) and Key Vault secret values into parameters.bicepparam:
cd azure\infrastructure
.\scripts\restore-AICondorDeploymentParamToBicepParams.ps1 -DryRun
Use this when bootstrapping a new workstation, validating published config, or rebuilding local deployment parameter files.