地形图案
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 运维部署
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Azure Terraform Patterns Skill
Composable architecture building blocks for Azure Terraform. Complements
`iac-terraform-best-practices.instructions.md` (style) and `azure-defaults` skill (naming, tags, regions).
> **Canonical sources** — the security baseline, AVM-first mandate, naming
> conventions, required tags, and unique-suffix rule live in
> [`azure-defaults/SKILL.md`](../azure-defaults/SKILL.md) and
> [`iac-policy-compliance.md`](../../instructions/references/iac-policy-compliance.md).
> This skill restates the rules tersely below for IaC-output convenience
> only; in conflict, the canonical sources win.
---
## Quick Reference
| Pattern | When to Use | Reference |
| ------------------------ | ------------------------------------------------ | ------------------------------------------ |
| Hub-Spoke Networking | Multi-workload environments with shared services | `references/hub-spoke-pattern.md` |
| Private Endpoint Wiring | Any PaaS service requiring private connectivity | `references/private-endpoint-pattern.md` |
| Diagnostic Settings | Every deployed resource (mandatory) | `references/common-patterns.md` |
| Conditional Deployment | Optional resources controlled by variables | `references/common-patterns.md` |
| Module Composition | Calling multiple AVM modules in root module | See inline example below |
| Managed Identity | Any service-to-service authentication | `references/common-patterns.md` |
| Budget & Cost Monitoring | Every deployment (mandatory) | `references/budget-pattern.md` |
| Plan Interpretation | Pre-deployment validation and change analysis | `references/plan-interpretation.md` |
| AVM Pitfalls | Set-type diffs, provider pins, 4.x changes | `references/avm-pitfalls.md` |
| AVM Authoring | AVM certification requirements, compliance | `references/avm-authoring-requirements.md` |
| Module Refactoring | Monolith → module extraction, state migration | `references/refactor-module.md` |
---
## Canonical Example — Module Composition
Wire AVM child modules by passing outputs as inputs (`module.<name>.<output>`); never
hardcode IDs. **AVM-TF module versions in APEX-generated code MUST be exact semver
(`version = "X.Y.Z"`)** — pinned at plan time from
`registry.terraform.io` (newest stable in `modules[0].versions[]`). Range
constraints (`~> X.Y`, `>= X.Y.Z`) are NOT allowed in `04-iac-contract.json` and
will be flagged by `npm run validate:avm-versions`. Full code sample
(resource group + key vault) and rationale in
[`references/module-composition.md`](references/module-composition.md).
---
## Rules
- **AVM-first**: Use `Azure/avm-res-*` registry modules over raw `azurerm_*` resources
- **AVM-TF version pins**: Exact semver only (`version = "X.Y.Z"`) — resolve the latest stable via `registry.terraform.io/v1/modules/Azure/avm-res-{path}/azurerm/versions` at plan time. Stale pins need a `pin_policy.mode = "exception"` block in `04-iac-contract.json`. Range constraints (`~>`, `>=`) are flagged by `validate:avm-versions`.
- **Hub-spoke**: Spokes peer to hub only; never spoke-to-spoke
- **Private endpoints**: Three resources per service — PE, DNS zone, VNet link
- **Diagnostics**: Every resource MUST have a diagnostic setting → Log Analytics
- **Conditional**: Use `for_each` (keyed) over `count` (indexed) for named resources
- **Identity**: SystemAssigned managed identity + RBAC; avoid keys/connection strings
- **Provider pin**: `~> 4.0` (allows 4.x patches, blocks 5.0)
- **Telemetry**: Set `enable_telemetry = false` in restricted-network environments
- **Moved blocks**: Use `moved {}` when renaming resources to prevent destroy/recreate
- **Budget**: 3 forecast thresholds (80%/100%/120%); amount and emails MUST be variables
## Steps
Applying a Terraform pattern in a root module:
1. **Identify the pattern** — match your need to a row in [Quick Reference](#quick-reference) (hub-spoke, private endpoint, diagnostics, conditional, identity, budget, plan interpretation)
2. **Load the reference** — read the linked `references/*.md`; do not load all at once
3. **Compose AVM modules** — wire outputs as inputs (see [Canonical Example](#canonical-example--module-composition)); never hardcode IDs
4. **Pin the provider** — `~> 4.0` only; do not use `>= 3.0` or exact `= 4.x.y`
5. **Add diagnostics + budget** — every resource gets a diagnostic setting; every deployment gets a budget with 80%/100%/120% forecast alerts
6. **Plan before apply** — `terraform plan -out=plan.tfplan`; review for `~`/`-`/`+/-` operations against [`references/plan-interpretation.md`](references/plan-interpretation.md)
7. **Validate** — `terraform fmt -check`, `terraform validate`, `npm run validate:terraform`, `npm run validate:iac-security-baseline`
## Gotchas
- **Set-type phantom diffs** — `azurerm_application_gateway`, `azurerm_lb`,
`azurerm_network_security_group`, `azurerm_firewall`, `azurerm_frontdoor`:
adding ONE element causes ALL elements to show `~` changes. Mitigation:
`ignore_changes` on set-type blocks.
- **Provider pin `~> 4.0` is critical** — `>= 3.0` crosses breaking
versions; `= 4.1.0` blocks patches. MUST use `~> 4.0`.
- **`for_each` over `count` for named resources** — `count` causes drift
when items are inserted/removed (Terraform reindexes).
Use `for_each = toset()`.
- **`moved` block required for renaming** — Renaming a resource ID
without a `moved {}` block causes destroy + recreate.
- **azurerm 4.x renamed attributes** —
`allow_blob_public_access` → `allow_nested_items_to_be_public`;
`enable_https_traffic_only` → `https_traffic_only_enabled`;
`azurerm_app_service` removed → use `azurerm_linux_web_app`.
---
## Reference Index
| File | Contents |
| ------------------------------------------ | ----------------------------------------------------------------- |
| `references/hub-spoke-pattern.md` | Full hub & spoke VNet + peering HCL |
| `references/private-endpoint-pattern.md` | PE + DNS zone + VNet link HCL, subresource table |
| `references/common-patterns.md` | Diagnostics, conditional deployment, module composition, identity |
| `references/budget-pattern.md` | Consumption budget, forecast alerts, anomaly detection |
| `references/plan-interpretation.md` | Plan commands, change symbols, red flags, summary script |
| `references/avm-pitfalls.md` | Set-type diffs, provider pins, tag ignore, moved blocks, 4.x |
| `references/tf-best-practices-examples.md` | Best-practice code examples, formatting, code review checklist |
| `references/bootstrap-backend-template.md` | Backend bootstrap template |
| `references/deploy-script-template.md` | Deployment script template |
| `references/project-scaffold.md` | Project scaffolding structure |
| `references/avm-authoring-requirements.md` | AVM certification: 37 requirements, compliance checklist |
| `references/refactor-module.md` | Module extraction, state migration, refactoring patterns |
| `references/module-composition.md` | Canonical AVM module composition example with output wiring |
---
> Source: [aivandelindt/azure-agentic-infraops](https://github.com/aivandelindt/azure-agentic-infraops) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
快速参考
典型示例——模块组成
规则
步骤
陷阱
文件/命令 -> iac-terraform-best-practices.instructions.md · azure-defaults · azure-defaults/SKILL.md · iac-policy-compliance.md · references/hub-spoke-pattern.md · references/private-endpoint-pattern.md · references/common-patterns.md · references/budget-pattern.md
内容校验值 -> c3eda501a7e3
当前原文的自动摘译,尚未人工审校。
快速参考
模式 · 何时使用 · 参考中心辐射网络 · 具有共享服务的多工作负载环境 ·
references/hub-spoke-pattern.md专用端点接线 · 任何需要专用连接的 PaaS 服务 ·references/private-endpoint-pattern.md诊断设置 · 每个部署的资源(强制) ·references/common-patterns.md有条件部署 · 由变量控制的可选资源 ·references/common-patterns.md典型示例——模块组成
通过将输出作为输入来连接 AVM 子模块 (
module.<name>.<output>);切勿对 ID 进行硬编码。 APEX 生成的代码中的 AVM-TF 模块版本必须是精确的 semver (version = "X.Y.Z") — 在计划时从registry.terraform.io固定(modules[0].versions[]中的最新稳定版)。04-iac-contract.json中不允许范围约束(~> X.Y、>= X.Y.Z)并且规则
AVM-first:在原始
azurerm_*资源上使用Azure/avm-res-*注册表模块 AVM-TF 版本引脚:仅精确语义版本 (version = "X.Y.Z") — 在计划时通过registry.terraform.io/v1/modules/Azure/avm-res-{path}/azurerm/versions解析最新的稳定版。陈旧的引脚需要在04-iac-contract.json中使用pin_policy.mode = "exception"块。范围约束(~>,>=)由validate:avm-versions标记。步骤
在根模块中应用 Terraform 模式: 识别模式 — 将您的需求与快速参考中的一行相匹配(中心辐射、专用端点、诊断、条件、身份、预算、计划解释) 加载参考 — 阅读链接的
references/*.md;不要一次加载所有 Compose AVM 模块 - 将输出连接为输入(请参阅规范示例);切勿对 ID 进行硬编码 固定提供商 — 仅~> 4.0;不要使用>= 3.0或确切的= 4.x.y陷阱
设置类型虚拟差异 —
azurerm_application_gateway、azurerm_lb、azurerm_network_security_group、azurerm_firewall、azurerm_frontdoor:添加一个元素会导致所有元素显示~更改。缓解措施:在集合类型块上ignore_changes。提供商 pin~> 4.0至关重要 —>= 3.0交叉断裂