Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Handles deployment of containerized applications to Azure Container Apps using the Azure Developer CLI (azd). Covers azure.yaml configuration, Bicep infrastructure modules, remote builds via ACR, environment variable flow across local and cloud environments, and managed identity RBAC setup.
azd combines Bicep provisioning, ACR image builds, and Container App deployment into a single idempotent command, removing the need to manually coordinate each Azure CLI step.
When to use it
- Deploying a containerized frontend and backend to Azure Container Apps
- Setting up idempotent Bicep infrastructure for repeatable provision runs
- Configuring remote ACR builds to avoid ARM/AMD64 architecture mismatches on M1 Macs
- Managing environment variables across dev, staging, and production azd environments
- Assigning managed identity RBAC roles to Container Apps after provisioning
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Deploy my Python backend and TypeScript frontend to Azure Container Apps with managed identity access to Azure OpenAI
- 1Creates azure.yaml defining frontend and backend services with remoteBuild: true and host: containerapp
- 2Writes main.bicep with a Container Apps environment, ACR, and system-assigned identity for the backend
- 3Configures main.parameters.json to inject azd env variables into Bicep parameters
- 4Adds a postprovision hook that runs az role assignment create to grant the backend Cognitive Services OpenAI User access
- 5Runs azd up to provision infrastructure, build images remotely in ACR, and deploy both services
Frontend and backend running on Azure Container Apps, backend managed identity granted RBAC access to Azure OpenAI, service URIs written to .azure/<env>/.env
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.