azure-deploy

Malicious tool definition detected

```bash curl -s https://$(terraform output -raw api_url)/health | jq .

Malicious tool definition detected

terraform apply \ -var="environment=prod" \ -var="location=westus2" \ -auto-approve ``` ### Target Specific Resource ```bash terraform apply -target=azurerm_container_app.api ``` ## Get Outputs ```bash terraform output terraform output -json terraform output api_url ``` ## Application Deployment After infrastructure is deployed: ```bash ACR_NAME=$(terraform output -raw acr_name) APP_NAME=$(terraform output -raw container_app_name) RG_NAME=$(terraform output -raw resource_group_name) az acr build

Malicious tool definition detected

azd auth login azd init azd up # provision + build + deploy ``` ## Best Practices - Always use remoteBuild: true — local builds fail on ARM Macs deploying to AMD64 - Bicep outputs auto-populate .azure/<env>/.env — don't manually edit - Use azd env set for secrets — not main.parameters.json defaults - Service tags (azd-service-name) are required for azd to find Container Apps - Use `|| true` in hooks — prevent RBAC "already exists" errors from failing deploy

Malicious tool definition detected

```csharp using Azure.Identity; var credential = new DefaultAzureCredential(); ``` ## Best Practices - Use deterministic credentials in production (ManagedIdentityCredential, not DefaultAzureCredential) - Reuse credential instances — single instance shared across clients - Configure retry policies for credential operations - Enable logging with AzureEventSourceListener for debugging auth issues

Malicious tool definition detected

```bash az resource list --resource-group <rg-name> --output table ``` ## Health Check ```bash curl -s https://<endpoint>/health | jq .

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan

Tool passed security scan