asd automation — YAML-driven flowsRun named tasks declared in
asd.yaml'sautomation:block. The same mechanismasd up,asd down, andasd run <task>use under the hood — exposed for direct invocation.
asd automation is the low-level verb. Most users reach asd up or
asd run <task> first. Drop to asd automation run when you need
to execute a one-off automation file outside the asd.yaml's named
tasks.
| Command | What it does |
|---|---|
asd automation run <file> |
Run an automation YAML file (steps, assertions, lifecycle hooks). |
asd automation yaml |
Print the automation YAML schema reference (also via asd schema automation). |
The schema lives in asd.yaml under automation:, but standalone
files (passed to asd automation run) have the same shape:
# example automation file
up:
- run: "docker compose up -d"
- run: "pnpm dev"
background: true
- assert: { http: "http://localhost:3000/healthz", status: 200, timeout: 30 }
down:
- run: "docker compose down"
Each step is either a run: (shell command), a reloadDotenv: true,
or an assert: (condition check). Steps run sequentially unless
background: true.
For the authoritative schema (every field, every type), run
asd schema automation — that's the source of truth.
| Goal | Command |
|---|---|
Run the project's up task |
asd up (preferred) or asd automation run asd.yaml --task=up |
| Run a one-off automation file | asd automation run scripts/deploy.yml |
| See the schema | asd schema automation (or asd automation yaml) |
Stop everything started by up |
asd down |
cli/starter §3 — asd up is the user-facing wrapper.learn/07-build-a-module — plugins contribute automation steps that get merged into the project's up task.asd schema automation — full YAML reference.