Question

A platform engineer runs 'terraform plan' on a large configuration and notices it completes quickly, showing an accurate diff of what will change without exhaustively querying every attribute of every resource from scratch. A teammate asks how Terraform knows the current configuration-to-resource relationships so efficiently. What is the primary mechanism enabling this behavior?

Accepted Answer

Terraform stores a record of managed resources and their last-known attributes in state, which it uses as the baseline to compute the diff against the desired configuration.

Answer

Terraform re-reads the entire provider API for all resource types on every plan and caches nothing between runs.

Answer

Terraform relies on cloud provider tags to identify which resources it manages and rebuilds relationships from those tags each run.

Answer

Terraform parses the git commit history of the configuration to determine what changed since the last apply.