Skip to content

Stackorder: Terraform and OpenTofu orchestration on GitHub Actions

Which stacks, in what order. Stackorder plans every stack a pull request affects and applies them in dependency waves on GitHub Actions. Open source and self-hosted, and by default the server holds no cloud credentials.

The Stackorder mark, three flat plates with the middle one offset to the rightThe Stackorder mark, three flat plates with the middle one offset to the right

The smallest setup ​

Stackorder works with GitHub.com, S3 state and AWS roles through GitHub OIDC. Current release: v0.6.0.

A repository needs a root stackorder.yaml, two thin workflow files, and the Stackorder GitHub App installed. Everything has a default, so the smallest valid configuration is one line:

yaml
version: 1

Stacks are discovered under stacks/** wherever a directory holds a terraform block with a backend "s3". A change to a local module, a directory a module block points at with a relative source, reaches every stack that uses it. Explicit dependencies between stacks go in a .stackorder.yaml next to the stack:

yaml
depends_on:
  - stacks/prod/vpc
  - acme/network-infra//stacks/prod/tgw

Continue with Getting started, or read How it works first.

Coming from a hand-written workflow? Terraform on GitHub Actions starts from plan on pull request and apply on merge, and shows what Stackorder adds across many stacks.