Skip to content
sluiceway
Go to console
Go to console

One issue. Every stack. Your tick.

Sluiceway keeps one GitHub issue that shows which Pulumi, OpenTofu, Terraform, Helm or Kubernetes stacks have changes waiting, and deploys a stack when you tick its box. Nothing deploys unless a person asks, or unless your own sluiceway.yaml says a stack goes out on merge.

Sluiceway is in beta. Pin a release commit to review every update before it runs.

Get startedWhat it looks like

These docs describe Sluiceway v0.50.2 · Changelog · Apache-2.0

Penny, the sluice gate, holding back three crates of pending changesPenny, the sluice gate, holding back three crates of pending changes

How it works

Section titled “How it works”

  1. After a merge to the default branch, and once a day, a scan previews the stacks in the repo.

  2. The scan writes the dashboard issue: one row per stack, and a box on every stack that has changes waiting.

  3. You tick a box.

    That asks for that stack to be deployed exactly as its row shows it.

  4. Sluiceway checks that you may tick that stack, and previews it again.

    It deploys only if the fresh preview still matches the row.

  5. The row goes back to in sync, or says why the deploy failed, with a link to the run.

Gate closed, water calm. Nothing to deploy.

Penny, the sluice gate, resting on a calm quay because every stack is in syncPenny, the sluice gate, resting on a calm quay because every stack is in sync

Where to go next

Section titled “Where to go next”

Get started

Install the GitHub App. It opens one pull request with the workflow and a first sluiceway.yaml, and the console guides the rest.

Credentials

Load your cloud and state credentials on Sluiceway’s step or in a step right before it, or name an env file that Sluiceway reads and masks.

Using the dashboard

Read the rows, tick a box to deploy a stack, and read the job log.

Without the app, run the action yourself: the same deploys, with the issue as the only dashboard. How the app and the action work together says what each one does.

The guides, in order:

Every key is in the sluiceway.yaml reference. What Sluiceway writes documents the markers, the deployment records and the result file for a script or an agent that reads them. The decision records say why Sluiceway works the way it does.