InfraDots logo
Documentation

Quick Reference

One-page summary for developers and engineers using InfraDots with Terraform or OpenTofu.

CLI vs InfraDots

Use caseWhere to run
Local experimentation, plan on your machineterraform / tofu CLI
Production applies, team runs, audit trailInfraDots (UI or API)
State for shared workInfraDots (remote, encrypted)

You can use the CLI and InfraDots together: same repo, same code; configure the remote backend if you want the CLI to use InfraDots state.

Versions

  • Engine — InfraDots supports Terraform and OpenTofu; choose per workspace.
  • Recommended — OpenTofu 1.6+ or Terraform 1.5+.
  • In code — Set required_version in a terraform {} block so everyone (and InfraDots) uses a consistent version.

Backend and state

  • Runs in InfraDots — State is stored by InfraDots; no local terraform.tfstate by default.
  • Local CLI — To use InfraDots state from your machine, configure the remote backend (see From local to InfraDots).

Variables and secrets

  • Terraform variables — Set in InfraDots (workspace or organization) with the same key as in your variable "..." block.
  • Secrets — Store in InfraDots as sensitive variables or environment variables; never commit them to the repo.
  • Provider credentials — Use environment variables (e.g. AWS_ACCESS_KEY_ID) and mark them sensitive.

Triggers

  • Manual — Start a plan or apply from the InfraDots workspace.
  • VCS — Connect a repo; runs can be triggered on push (configurable per workspace).
  • Schedule — Use workspace schedules for recurring plan/apply (e.g. drift detection).
Glossary