Deployment Reference

Azure CLI with PowerShell Deployment

Use the script-driven Azure CLI and PowerShell deployer when you want more sequencing control than the default AZD flow.

Script-driven rollout Container App Service model Direct sequencing control
Deployment reference Upgrade paths

This deployer keeps you in the repo’s container-based deployment model while giving you more direct script control over sequencing, retries, and environment-specific adjustments.

Script-first operations

Use this when you want the deployment flow to live in PowerShell instead of AZD orchestration commands.

Explicit sequencing

The script-driven model makes it easier to reason about recovery steps and operational checkpoints in environments that prefer scripted control.

Same runtime model

This path still deploys the containerized App Service runtime, so Gunicorn startup stays with the container entrypoint.

Key scripts

The main flow lives in deployers/azurecli/deploy-simplechat.ps1, with destroy/reset support in the paired cleanup script.

Keep the runtime rule consistent

This deployer targets container-based Azure App Service. Do not add the native Python startup command for this path unless you intentionally change deployment models.

When to choose this path

  • You want a script-driven deployment flow without azd
  • You want more direct control over sequencing and recovery steps
  • You still want the repo’s container-based App Service deployment model

Main files

  • deployers/azurecli/deploy-simplechat.ps1
  • deployers/azurecli/destroy-simplechat.ps1

Quick start

  1. Review the variables near the top of deploy-simplechat.ps1.
  2. Sign in to the target Azure cloud and subscription.
  3. Run the deployer from PowerShell or pwsh.
cd deployers/azurecli
./deploy-simplechat.ps1

References