8.1.1. Workspaces and Remote Operations
💡 First Principle: An HCP Terraform workspace is a managed unit of one state plus its runs and variables — so organizing infrastructure becomes "how do I split it into workspaces," and each workspace gets shared state and automatic locking for free.
In HCP Terraform, a workspace holds a single state file, its variables, and its run history — roughly equivalent to one Terraform working directory, but managed centrally. Remote operations mean plan and apply execute on HCP Terraform's infrastructure rather than locally, giving consistent execution environments, a shared audit log of runs, and automatic state storage and locking.
⚠️ Exam Trap: HCP Terraform workspaces are not the same as CLI workspaces (terraform workspace). CLI workspaces are multiple named state files within one backend/directory; HCP workspaces are managed units that more closely resemble separate working directories with their own variables and run history.
Reflection Question: Why does running plans and applies remotely (rather than on each engineer's machine) improve both consistency and auditability?
