iac-common

Provide shared Azure IaC patterns for Bicep and Terraform deployments.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/pazdedav/my-infraops-project --skill iac-common
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iac-common
Source: https://github.com/pazdedav/my-infraops-project/tree/main/.github/skills/iac-common
Command: npx skills add https://github.com/pazdedav/my-infraops-project --skill iac-common

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides standardized, safe, and efficient patterns for Infrastructure as Code (IaC) deployments on Azure, ensuring consistency and reducing common errors across Bicep and Terraform.

Core Features & Use Cases

  • Authentication Validation: Ensures robust Azure CLI authentication before deployments.
  • Deployment Strategies: Defines phased and single deployment approaches for better control.
  • Known Issues & Workarounds: Centralizes common problems and their solutions for both Bicep and Terraform.
  • Governance Mapping: Translates Azure Policy constraints into IaC properties.
  • Circuit Breaker: Implements safety mechanisms to halt deployments upon repeated failures.
  • Use Case: When deploying a new Azure environment, use this Skill to ensure the deploy agent validates authentication correctly, follows a phased deployment strategy, and automatically applies workarounds for known issues like stale tokens in devcontainers.

Quick Start

Ensure the deploy agent validates Azure CLI authentication using the two-step check before proceeding with any 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 Terraform or Bicep deployments?

Validating Azure CLI authentication before deployments requires a two-step check to ensure robust credentials and prevent failures. This process verifies the active session state before the deploy agent proceeds with any Infrastructure as Code execution.

What are common Bicep and Terraform deployment issues on Azure and how do I work around them?

Common Bicep and Terraform deployment issues on Azure include stale authentication tokens in devcontainers. Centralized workarounds automatically apply fixes for these known Infrastructure as Code problems to ensure standardized deployment processes.

How do I map Azure Policy governance constraints into Infrastructure as Code properties?

Mapping Azure Policy governance constraints into Infrastructure as Code properties translates compliance rules directly into Bicep and Terraform configurations. This ensures deployments meet organizational standards without manual policy verification.

Can I implement a circuit breaker to halt Azure IaC deployments upon repeated failures?

Implementing a circuit breaker for Azure IaC deployments automatically halts the process upon repeated failures. This safety mechanism prevents cascading errors during both phased and single deployment strategies.

What is a phased deployment strategy for Azure Infrastructure as Code?

A phased deployment strategy for Azure Infrastructure as Code breaks down environment provisioning into controlled stages. This approach provides better control over Bicep and Terraform executions compared to single deployment methods.