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.
In more detail
HCP stands for HashiCorp Cloud Platform; the service used to be called Terraform Cloud. A configuration connects to it with a cloud block inside the terraform block, in place of a backend block. Its workspaces are larger than CLI workspaces: each one has its own state, variables, permissions and run history, much like a separate configuration directory.
Related terms
- Terraform backend — The setting that decides where Terraform stores state and how it locks it, from a local file to shared cloud storage.
- Terraform workspace — A named, separate state within one backend, so the same configuration can manage several copies of its infrastructure.
- remote state — Reading another configuration's output values from its state, using the terraform_remote_state data source.
Taught in
- Configuring A Remote Backend — Infrastructure as Code with Terraform
- Workspaces For Multiple Environments — Infrastructure as Code with Terraform
- One Hour, No Weights Published — HashiCorp Terraform Associate (004) Exam Prep
- Infrastructure As Code, And One Workflow For Every Platform — HashiCorp Terraform Associate (004) Exam Prep
- Providers: How Terraform Reaches Every API — HashiCorp Terraform Associate (004) Exam Prep
- State: Terraform's Memory Of What It Built — HashiCorp Terraform Associate (004) Exam Prep
- Input Variables, Outputs, And Which Value Wins — HashiCorp Terraform Associate (004) Exam Prep
- Dependencies, depends_on And Lifecycle Rules — HashiCorp Terraform Associate (004) Exam Prep
- Where Modules Come From — HashiCorp Terraform Associate (004) Exam Prep
- The Local Backend, And Workspaces On One Machine — HashiCorp Terraform Associate (004) Exam Prep