InfraDots logo
Documentation

Glossary

Quick reference for terms used in the InfraDots and Terraform/OpenTofu documentation.

Terraform / OpenTofu

TermDefinition
ApplyRun that executes a plan and updates real infrastructure (and state).
BackendWhere Terraform/OpenTofu stores state (e.g. local file, S3, or InfraDots remote).
HCLHashiCorp Configuration Language — the language used in .tf files.
ModuleReusable bundle of Terraform/OpenTofu configuration (inputs, resources, outputs).
OutputValue exported after apply (e.g. bucket name, URL) for use by other systems or modules.
PlanDry run that shows what would be added, changed, or destroyed without making changes.
ProviderPlugin that talks to a cloud or service (e.g. AWS, GCP, Kubernetes).
ResourceA single piece of infrastructure (e.g. an S3 bucket, a VM) defined in configuration.
StateRecord of resources Terraform/OpenTofu manage; used to plan updates and avoid duplicates.
VariableInput to configuration (declared in variable "name" {}, set via UI, CLI, or env).

InfraDots

TermDefinition
OrganizationTop-level container for workspaces, members, and billing.
RunA single execution of plan, apply, or destroy in a workspace.
WorkspaceRepresents one Terraform/OpenTofu configuration (one state, one repo/path, one version).
Worker poolSet of execution agents you run; runs can be assigned to a pool for in-your-network execution.
VCS providerConnection to GitHub, GitLab, etc., used to link repos to workspaces and trigger runs.
IDP AgentInfraDots feature that reviews plans and code for best practices and security.

General

TermDefinition
DriftWhen real infrastructure no longer matches state (e.g. someone changed it in the cloud console).
IaCInfrastructure as Code — defining and managing infrastructure with configuration files and automation.