Agent Skills
› cosmicstack-labs/mercury-agent-skills
› terraform-iac
terraform-iac
GitHub提供Terraform基础设施即代码的最佳实践，涵盖状态管理、模块化设计、远程后端配置及多环境策略，指导安全规范的云资源编排。
触发场景
使用Terraform管理云基础设施
配置Terraform远程状态和模块
规划多环境部署架构
安装
npx skills add cosmicstack-labs/mercury-agent-skills --skill terraform-iac -g -y
SKILL.md
Frontmatter
{
"name": "terraform-iac",
"metadata": {
"tags": [
"terraform",
"iac",
"infrastructure",
"cloud",
"devops"
],
"author": "cosmicstack-labs",
"version": "1.0.0",
"category": "devops"
},
"description": "State management, modules, workspaces, remote backends, and multi-environment strategies"
}
Terraform / Infrastructure as Code
Manage infrastructure with Terraform.
Core Concepts
State Management
- Store state remotely (S3, Terraform Cloud)
- Enable state locking (DynamoDB)
- Never edit state manually (use
terraform statecommands) - Isolate environments with workspaces or directories
Structure
terraform/
├── modules/
│ ├── networking/
│ ├── compute/
│ └── database/
├── environments/
│ ├── dev/
│ │ ├── main.tf
│ │ ├── variables.tf
│ │ └── terraform.tfvars
│ ├── staging/
│ └── production/
└── backend.tf
Module Design
Module Interface
# modules/compute/main.tf
variable "instance_type" { type = string }
variable "subnet_id" { type = string }
output "instance_id" { value = aws_instance.app.id }
Module Best Practices
- Input validation (type constraints, validation blocks)
- Outputs for all useful values
- Versioned modules (Git tags, registry)
- Documentation (README per module)
- Test with Terratest
Remote Backend
terraform {
backend "s3" {
bucket = "my-terraform-state"
key = "production/terraform.tfstate"
region = "us-east-1"
dynamodb_table = "terraform-locks"
encrypt = true
}
}
Multi-Environment Strategy
- Workspaces: Simple, state separation only
- Directory structure: Full isolation, can diff configs
- Terragrunt: DRY config, repeatable structure
- Always: Plan in CI, approve, then apply
- No manual applies in production
版本历史
- 38e2523 当前 2026-07-05 19:39
