azd-deployment
Deploy to Azure Container Apps with azd
This skill provides documentation and reference examples for deploying containerized applications to Azure Container Apps using Azure Developer CLI (azd) and Bicep infrastructure templates.
Descargar el ZIP de la skill
Subir en Claude
Ve a Configuración → Capacidades → Skills → Subir skill
Activa y empieza a usar
Pruébalo
Usando "azd-deployment". How do I deploy a container app with azd?
Resultado esperado:
Run: azd auth login, azd init, azd env new <env-name>, azd up. The azure.yaml defines services with host: containerapp and remoteBuild: true for Azure-based builds.
Usando "azd-deployment". What is the azure.yaml structure?
Resultado esperado:
Define services with project path, language (ts, python, etc.), host: containerapp, and docker config. Use infra.provider: bicep for infrastructure. Add hooks for preprovision, postprovision, postdeploy actions.
Auditoría de seguridad
SeguroThis skill is legitimate DevOps documentation for Azure Container Apps deployment. All detected patterns (external commands, network, filesystem) are standard Azure CLI operations used in deployment workflows. The heuristic alerts about credential access and command execution are false positives - the skill contains only documentation and example configurations, not actual credential handling or malicious code.
Factores de riesgo
⚙️ Comandos externos (3)
🌐 Acceso a red (2)
📁 Acceso al sistema de archivos (3)
Puntuación de calidad
Lo que puedes crear
Set up new azd project
Initialize a new Azure Developer CLI project with proper azure.yaml configuration for container apps deployment
Configure Bicep infrastructure
Create reusable Bicep modules for container apps environment, with outputs that auto-populate environment variables
Implement CI/CD hooks
Add preprovision, postprovision, and postdeploy hooks for RBAC assignments and custom domain handling
Prueba estos prompts
Show me how to initialize a new azd project for deploying to Azure Container Apps with a Python backend.
Create an azure.yaml configuration for a TypeScript frontend and Python backend deployed to container apps with remote builds enabled.
How do I configure Bicep outputs so they automatically populate environment variables in the .azure folder?
Show me how to assign RBAC roles to a container app managed identity for Azure OpenAI and AI Search access using postprovision hooks.
Mejores prácticas
- Always use remoteBuild: true in azure.yaml to avoid AMD64/M1 architecture mismatch
- Use azd env set for secrets instead of hardcoding in main.parameters.json
- Add || true to RBAC hook commands to prevent failures when roles already exist
Evitar
- Using local build instead of remoteBuild will fail on ARM Macs deploying to AMD64 Azure
- Manually editing .azure/<env>/.env files - these are auto-populated by Bicep outputs
- Skipping the resourceToken in internal DNS names - required for unique service discovery