What is the benefit of the numbered layer architecture?

Numbering directories (e.g., 00_network, 10_security) visually encodes the dependency order. This makes it immediately obvious which layers are prerequisites for others and ensures the deployment chain remains acyclic.

How do layers communicate if they have separate state files?

Higher-numbered layers use Terraform remote state data sources to read specific outputs from lower-numbered layers. This creates an explicit, auditable, and one-way dependency chain.

Does this skill support AWS, GCP, and Azure?

Yes, the core principles of repository and state strategy are cloud-agnostic. The skill provides specific implementation patterns for S3 (AWS), GCS (GCP), and Azure Blob Storage backends.

Why should I avoid monolithic Terraform state files?

Monolithic states create a massive blast radius where a single error or state corruption can destroy your entire infrastructure. They also cause slow plan times and prevent multiple teams from working on different components in parallel.

Terraform Repository & State Strategy

Name: Terraform Repository & State Strategy
Author: oborchers

byoborchers

•

Cloud Infrastructure

Architects resilient cloud infrastructure using multi-repository strategies and numbered layer state isolation to minimize blast radius.

This skill provides expert guidance on structuring Terraform projects for maximum scalability and safety by moving away from monolithic state files toward a modular, layered architecture. It helps users implement numbered directory patterns (e.g., 00_network, 10_security) to encode dependency orders and enforces a strict 'one state file per layer per environment' policy. By following these research-backed principles, developers can reduce deployment risks, improve CI/CD isolation, and maintain clear ownership across complex cloud environments while ensuring state files are secure, versioned, and locked.

Key Features

019 GitHub stars

02Numbered layer architecture (00-90) to explicitly encode resource dependency and execution order.

03Security-first state management including mandatory encryption, versioning, and locking configurations.

04Implementation patterns for cross-layer remote state references across AWS, GCP, and Azure.

05Multi-repository strategy for organizational, shared, and service-specific infrastructure isolation.

06State isolation strategy requiring one state file per layer per environment to minimize blast radius.

Use Cases

01Designing a new multi-environment cloud foundation with clear dependency chains and ownership.

02Establishing CI/CD pipelines that isolate infrastructure changes by change cadence and risk profile.

03Refactoring a monolithic Terraform state file into a safer, modular layered architecture.

Key Features

019 GitHub stars

02Numbered layer architecture (00-90) to explicitly encode resource dependency and execution order.

03Security-first state management including mandatory encryption, versioning, and locking configurations.

04Implementation patterns for cross-layer remote state references across AWS, GCP, and Azure.

05Multi-repository strategy for organizational, shared, and service-specific infrastructure isolation.

06State isolation strategy requiring one state file per layer per environment to minimize blast radius.

Use Cases

01Designing a new multi-environment cloud foundation with clear dependency chains and ownership.

02Establishing CI/CD pipelines that isolate infrastructure changes by change cadence and risk profile.

03Refactoring a monolithic Terraform state file into a safer, modular layered architecture.