One issue. Every stack. Your tick.

Sluiceway keeps one GitHub issue that shows which infrastructure stacks have changes waiting, and deploys a stack when you tick its box.

Sluiceway is in beta.

Apache-2.0 · v0.8.0

Gate closed, water calm. Nothing to deploy.

The panel above shows crates waiting. This picture shows nothing pending. The header of your dashboard always shows the real state of your stacks.

How it works

After a merge to the default branch, and once a day, a scan previews the stacks in the repo.
The scan writes the dashboard issue: one row per stack, and a box on every stack that has changes waiting.
You tick a box.
That asks for that stack to be deployed exactly as its row shows it.
Sluiceway checks that you may tick that stack, and previews it again.
It deploys only if the fresh preview still matches the row.
The row goes back to in sync, or says why the deploy failed, with a link to the run.

Add Sluiceway one step at a time, starting with a check that changes nothing.

Every key of sluiceway.yaml and what it changes.

The decision records say why Sluiceway works the way it does.