hashicorp /

Terraform

Live map
View repository
Snapshotmain · 6a24611

Terraform Core loads HCL, combines configuration with prior and remote state, asks provider plugins to plan changes, then applies the approved graph.

Click a building or route
Choose a path

Configuration and prior state form a graph; providers refresh reality and help calculate a reviewable change set.

System map8 components · 10 connections
130%
Terraform: configuration becomes a reviewed change graph architecturePlanning is the left-to-right path; applying loops the saved plan through providers, external APIs, and the state backend..tf files, variable va…modules, resources, ex…resource instances, pr…ordered evaluable vert…schema, configuration,…provider-specific API …Terraform CLIConfigurationloaderDependencygraphPlan engineProviderpluginsRemote APIsApply engineState backend
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal

Terms, in plain English

HCLHashiCorp Configuration Language, the syntax commonly used for Terraform configuration.

How to study this repo

  1. 1
    Separate configuration from state

    Read the config parser and state model; write down what each knows and why neither replaces the other.

  2. 2
    Inspect graph construction

    Walk through graph_builder_plan.go and identify transforms that add references, providers, state, and ordering.

  3. 3
    Trace provider RPCs

    Compare planning and apply calls in provider.go, then explain why the final state can contain computed values.