Skip to main content
Soundcheck infrastructure is deployed across multiple environments for development, testing, and production.

Environment summary


Development environment

Resources

Configuration

Deployment

Merging to dev branch triggers automatic deployment.

QA environment

Resources

Configuration

Deployment

Merging dev → qa triggers automatic deployment.

Production environment

Resources

Configuration

Scaling

  • Autoscaling: Enabled
  • Min instances: 2
  • Max instances: 5

Deployment

Merging qa → main requires approval, then triggers deployment.

Sandbox environment

Sandbox is for manual testing of infrastructure changes.

Setup

Deploy

Cleanup

Always destroy sandbox resources when done to avoid charges:

Environment variables

Each environment has its own tfvars file:

Generating tfvars

The generate-tfvars.sh script pulls secrets from Key Vault:

Promotion workflow


Access control

VPN access required

These resources require VPN in Dev/QA:
  • Database direct access
  • Key Vault management
  • Log Analytics dashboards
  • Internal APIs

Public access

These are publicly accessible:
  • App Service endpoints (production API App Service only)
  • Static Web App (frontend)
  • API health checks

Naming convention

Resources follow this naming pattern:
Examples:
  • prod-cus-api-app - Production API App Service (dev/qa no longer provision this)
  • qa01-cus-core-kv - QA Key Vault
  • prod-cus-db - Production Database