Run history: When Terraform Cloud manages a workspace's Terraform runs, it retains a record of all run activity, including summaries, logs, a reference to the changes that caused the run, and user comments. Refer to Terraform State in Terraform Cloud for more details. Although only the current state is necessary for managing resources, the state history can be useful for tracking changes over time or recovering from problems. State versions: Each workspace retains backups of its previous state files. In addition to the basic Terraform content, Terraform Cloud keeps some additional data for each workspace: In workspace, stored as sensitive variables In shell environment or entered at prompts tfvars files, as CLI arguments, or in shell environment In linked version control repository, or periodically uploaded via API/CLIĪs. Terraform Cloud workspaces and local working directories serve the same purpose, but they store their data differently: Component

Hands-on: Try the Create a Workspace tutorial on HashiCorp Learn. A workspace contains everything Terraform needs to manage a given collection of infrastructure, and separate workspaces function like completely separate working directories. Terraform Cloud manages infrastructure collections with workspaces instead of directories. Since Terraform CLI uses content from the directory it runs in, you can organize infrastructure resources into meaningful groups by keeping their configurations in separate directories. When run locally, Terraform manages each collection of infrastructure with a persistent working directory, which contains a configuration, state data, and variables. Working with Terraform involves managing collections of infrastructure resources, and most organizations manage many different collections.

Code ready workspaces