All integrationsCloud Computing

Terraform

Run HCP Terraform from your workflows: create and configure workspaces, set their variables, upload Terraform configuration, start plans and apply, discard or cancel runs, and read the outputs your infrastructure produces.

actions
20

Actions

Steps a workflow can run in Terraform.

  • List organizationsList the HCP Terraform organizations the token's user belongs to, with each one's plan.
  • List workspacesList an organization's workspaces, optionally searched by name or filtered by project, tag or the status of their current run.
  • Get workspaceGet a workspace's settings, lock state, resource count and current run, by its id, its name or its link.
  • Create workspaceCreate a workspace that is run from Lodol: upload its configuration with Upload configuration, then start runs with Create run.
  • Update workspaceChange a workspace's settings. Only the fields filled in change. Renaming a workspace changes its link.
  • Delete workspaceDelete a workspace. By default it is only deleted when it manages no resources; Force delete removes it anyway, leaving its infrastructure in place but no longer tracked.
  • Lock workspaceLock a workspace so no new run can start in it until it is unlocked.
  • Unlock workspaceUnlock a workspace. Force unlock releases a lock held by another user or a run.
  • Upload configurationUpload Terraform files to a workspace and wait until HCP Terraform has read them, so the next Create run uses them.
  • Create runStart a run in a workspace: a plan, then an apply once confirmed (or straight away with auto apply). Use Get run to follow it. A free organization runs one at a time, so others wait their turn.
  • List runsList a workspace's runs, newest first. Plan only runs are left out unless chosen under Operations. HCP Terraform allows this 30 times a minute, so follow one run with Get run instead.
  • Get runGet a run's status and what its plan and apply add, change and destroy. Repeat it to wait for a run to finish.
  • Apply runConfirm a run that is waiting for confirmation, so its plan is applied. The apply is queued; use Get run to see it finish.
  • Discard runDiscard a run that is pending or waiting for confirmation, so it is never applied. A run that is planning or applying is stopped with Cancel run instead.
  • Cancel runInterrupt a run that is planning or applying, like pressing Ctrl+C. A run that is pending or waiting for confirmation is stopped with Discard run instead.
  • List variablesList a workspace's Terraform and environment variables. Sensitive values come back empty.
  • Create variableAdd a Terraform variable or an environment variable to a workspace. Every later run uses it.
  • Update variableChange a workspace variable's key, value, description or category. Only the fields filled in change.
  • Delete variableRemove a variable from a workspace.
  • Get outputsGet the outputs of a workspace's latest state, such as an IP address or a URL the configuration produced. Sensitive outputs come back null.

Automate Terraform with Lodol.

Connect Terraform and ask your AI for your first workflow.

Free plan, no credit card