Skip to main content
August 24, 2026

Terraform stack modules

This feature is behind a feature flag. Reach out to our team if you would like it enabled for your organization.
Terraform has proven to be a powerful way to manage an install stack, but we felt the experience could be improved upon. There were 3 key areas we wanted to improve on:
  • Obviate the need for your customer to manage a large, complex tfvars file.
  • Stop relying on the phone home ID to secure the phone home request.
  • Make it easier for your customer to apply updates.
To that end, we are publishing new stack modules to the Terraform registry. These modules read the stack config directly from the control plane, so your customer no longer needs to paste in a tfvars file. Each stack is given a service account that can authenticate using a token. The phone_home_id no longer needs to be updated on every reprovision. Additionally, your customer can more easily control versioning via semver.
Once installed, your customers simply need to run terraform apply to install a new version of the stack. If new inputs or secrets are required, an actionable terraform error will be displayed. For example, if a new app version requires a_new_input, the customer will see this error until they set it.
To manage updates to the stack module itself, recommend setting a semver constraint on the minor version. That way your customer only needs to run terraform init -upgrade to receive patch updates. Minor and major versions can be received by updating the module version.
For more details, see the Provision Stack with a Terraform Module guide.