iac-common

Validate Azure CLI authentication and implement phased Bicep and Terraform deployments.

50|32|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/jonathan-vella/azure-agentic-infraops-accelerator --skill iac-common-jonathan-vella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iac-common
Source: https://github.com/jonathan-vella/azure-agentic-infraops-accelerator/tree/main/.github/skills/iac-common
Command: npx skills add https://github.com/jonathan-vella/azure-agentic-infraops-accelerator --skill iac-common-jonathan-vella

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides essential shared patterns and guardrails for Infrastructure as Code (IaC) deployments, ensuring secure authentication, consistent deployment strategies, and adherence to governance policies across both Bicep and Terraform.

Core Features & Use Cases

  • Secure Authentication: Validates Azure CLI authentication to prevent deployment failures due to stale tokens.
  • Phased Deployments: Implements a structured, multi-phase deployment approach for complex infrastructures, with user approval gates at each stage.
  • Governance Mapping: Translates Azure Policy constraints into IaC properties for consistent compliance.
  • Circuit Breaker: Implements robust error handling and stopping rules to prevent runaway deployments and ensure safe operations.
  • Use Case: Before deploying a new set of Azure resources using Bicep, this skill ensures the CLI is properly authenticated and outlines a phased deployment strategy, including security and data layers, with clear user approval steps.

Quick Start

Use the iac-common skill to validate Azure CLI authentication before proceeding with a Bicep deployment.

Frequently Asked Questions about iac-common

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Azure CLI authentication before running Bicep or Terraform deployments?

Phased IaC deployments split complex infrastructures into sequential stages with user approval gates between each phase, ensuring structured rollout, operational consistency, and safe execution for both Bicep and Terraform.

Can I map Azure Policy governance constraints directly into infrastructure as code properties?

An IaC circuit breaker mechanism prevents runaway infrastructure deployments by implementing robust error handling and strict stopping rules, halting operations automatically when critical deployment failures or anomalies are detected.

Does iac-common work with both Bicep and Terraform for Azure infrastructure provisioning?

Iac-common supports both Bicep and Terraform deployment agents by providing shared infrastructure as code patterns, ensuring consistent CLI authentication validation, deployment strategies, and governance mapping across both frameworks.

What is a phased deployment strategy in infrastructure as code and when do I need it?

A phased IaC deployment strategy splits complex infrastructures into sequential stages with user approval gates between each phase, ensuring structured rollout, operational consistency, and safe execution for both Bicep and Terraform.

How do I map Azure Policy constraints to Terraform or Bicep properties for compliance?

Mapping Azure Policy constraints to IaC properties translates governance rules directly into Bicep and Terraform code configurations, ensuring your deployments automatically adhere to organizational compliance and security standards.

Why do my Bicep deployments fail with stale Azure CLI tokens and how can I prevent it?

Bicep deployments fail with stale Azure CLI tokens when authentication expires, but implementing pre-deployment authentication validation prevents this by verifying active credentials and stopping operations before token-related failures occur.