deploy_azure.sh — deploy TaskFlow to Azure Container Apps

set -euo pipefail

RESOURCE_GROUP="taskflow-rg"

LOCATION="eastus"

CONTAINER_APP="taskflow-app"

IMAGE="ghcr.io/your-org/taskflow:latest"

echo "[INFO] Creating resource group..."

az group create --name "$RESOURC{E}_{G}ROUP"--location"$LOCATION"

echo "[INFO] Setting up Container Apps environment..."

az containerapp env create \

--name "taskflow-env" \

--resource-group "$RESOURCE_GROUP" \

--location "$LOCATION"

echo "[INFO] Deploying container..."

az containerapp create \

--name "$CONTAINER_APP" \

--resource-group "$RESOURCE_GROUP" \

--environment "taskflow-env" \

--image "$IMAGE" \

--target-port 8000 \

--ingress external \

--cpu 0.5 \

--memory 1.0Gi \

--min-replicas 1 \

--max-replicas 3 \

--query properties.configuration.ingress.fqdn

Claude can further validate configurations by checking for:

- Proper scaling thresholds.
- Missing ingress or HTTPS settings.
- Unused resource groups or dangling images.

The output includes a public FQDN, which you can then test withcurl or a browser.

Hands-On Example 3: Deploying to GCP Cloud Run

Claude can generate GCP commands with minimal configuration overhead:

“Claude, deploy my containerized FastAPI app to GCP Cloud Run with automatic HTTPS and service account authentication.”

GCP Deployment Script

```bash
#!/usr/bin/env bash

# deploy_gcp.sh — deploy TaskFlow API to GCP Cloud Run
set -euo pipefail

PROJECT_ID="taskflow-project"

SERVICE_NAME="taskflow"

REGION="us-central1"

IMAGE="gcr.io/${PROJECT_ID}/taskflow:latest"

echo "[INFO] Enabling required APIs..."

gcloud services enable run.googleapis.com artifactregistry.googleapis.com

echo "[INFO] Deploying container..."

gcloud run deploy "$SERVICE_NAME" \

--image "$IMAGE" \

--platform managed \

--region "$REGION" \

--allow-unauthenticated \

--memory 512Mi \

--port 8000 \

--max-instances 5

echo "[SUCCESS] Deployment complete."

gcloud run services describe "$SERVIC{E}_{N}AME"--region"$REGION" --format 'value(status.url)'

This entire flow—enabled by Claude—takes less than 10 minutes to deploy a production-grade container to Cloud Run.

Clarification Table: Claude’s Role Across Cloud Providers

Integrating with cloud providers is no longer an overwhelming process when Claude Code is part of your DevOps toolkit. Instead of memorizing every command or resource syntax, you focus on defining intent: what you want deployed, where, and under what constraints. Claude translates that intent into consistent, cloud-specific configuration—then verifies and refines it for performance and security.

In the next section, you’ll explore multi-environment management, where Claude helps you synchronize configurations between development, staging, and production, ensuring every environment behaves predictably without manual intervention or drift.