HCP Terraform workspace
The HCP Terraform container for one collection of infrastructure: its configuration source, variables, state, run history and team access.
In more detail
HCP Terraform workspaces are required; nothing can be managed without one. They differ from CLI workspaces, which only add another state for the same working directory and share its configuration, backend and credentials. Each HCP workspace belongs to exactly one project.
Example
booking-prod workspace in the booking projectRelated terms
- HCP Terraform project — A group of HCP Terraform workspaces that shares team access and default settings.
- Terraform workspace — A named, separate state within one backend, so the same configuration can manage several copies of its infrastructure.
- variable set — A named group of variables in HCP Terraform applied globally, to chosen projects, or to chosen workspaces.
- HCP Terraform — HashiCorp's hosted service for running Terraform, which keeps state, runs plans and applies on its own machines, and controls who may change what.
Taught in
- The Local Backend, And Workspaces On One Machine — HashiCorp Terraform Associate (004) Exam Prep
- HCP Workspaces, Projects And Variable Sets: Which Value Wins? — HashiCorp Terraform Associate (004) Exam Prep
- VCS, CLI And API Workflows: Speculative Plans And Run Triggers — HashiCorp Terraform Associate (004) Exam Prep
- Trap Sprint: Twelve Answers That Are Almost True — HashiCorp Terraform Associate (004) Exam Prep