stado product schema
Invocation
stado product schema [OPTIONS] --engine <engine> <operation>Purpose
Release steps of a database-schema product on any engine: sqlite, postgres or supabase
Required inputs and options
| Input or option | Contract |
|---|---|
<operation> | verify: the post-build test of a schema product; applies every migration, in file-name order, to a scratch database of the engine and reports the tables it made. sqlite and postgres read release/database-schema.tar, produced by source-bundle, never the current checkout. sqlite: a fresh file under $WISENT_OUTPUT_DIR/schema-verify. postgres: the scratch database WISENT_SCRATCH_DATABASE_URL names, through psql. supabase: $WISENT_OUTPUT_DIR/release/supabase-source.tar on a local Supabase stack (supabase db start, Supabase CLI and Docker on the runner) [possible values: verify] |
--catalog <catalog> | Independent authoritative catalog path |
--engine <engine> | The engine the schema runs on [possible values: sqlite, postgres, supabase] |
--migrations <migrations> | Directory inside database-schema.tar's source/ root; *.sql files run in file-name order (sqlite and postgres) [default: migrations] |
--workspace <workspace> | The workspace of canonical checkouts this operation reads and builds from; default WISENT_WORKSPACE, else ~/Documents/CodingProjects/Wisent |
--project-dir <project-dir> | Directory inside the bundle that holds supabase/ (supabase; default: the bundle root) [default: .] |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.