Skip to main content
Last updated on
Version: 1.0.0

Getting Started

This guide explains how the deployment framework works and how to run it safely for a new environment.

Prerequisites​

You’ll need:

  • Azure CLI (recent)
  • Permissions to create resources in the target subscription
  • Network access to Azure endpoints (DNS + outbound 443)
  • jq installed (scripts use it for some REST responses)

Workflow​

  1. Configure environment inputs in ./scripts/00_config.sh
  2. Run the scripts in numeric order (01 → 15)
  3. Validate at key checkpoints (networking, ACA environment, AppGW routing)

Branch and environment model​

  • BRANCH = product line / major release / customer variant (examples: EQ, P2P, ACME)
  • ENV = environment stage (examples: DEV, QA, STAGE, PROD)

Most resource names are derived from:

<branch>-<env>

What gets deployed​

At a high level, the scripts provision:

  • Resource Group
  • Storage Account + File Share (for volume mounts)
  • Key Vault
  • ACR integration
  • VNet + subnets (including delegated subnet for ACA environment)
  • Log Analytics + ACA Environment (internal)
  • Redis (Classic or Redis Enterprise)
  • MongoDB vCore (DocumentDB mongoClusters)
  • Container Apps (internal ingress)
  • Application Gateway (public entry point) with URL path-based routing to internal ACA services

Next steps​

Last updated on