Expand description
fz migrations apply (issue #18): applies the harness’s module
migrations directly to a Postgres database — the native counterpart of
wrangler d1 migrations apply. --fleet and --plan instead point
it at a control database and run the boot-time reconciliation the
native runtime runs (RECONCILIATION.md, issue #30) by hand.
The two are different databases and different work, so neither is the
other’s default. An earlier cut of #30 made --url mean the control
database always: against an ordinary venture database that
reconciled a registry with no tenants in it, printed nothing, and
exited zero having applied no migrations — including in
ROLLBACK.md’s recovery runbook, which runs this command to re-apply
what is missing. Silence and success are the two things a migration
step must never combine.
Requires building fz with cratefield-cli’s postgres feature so
sqlx and tokio stay out of the default (wasm-safe) dependency graph.
Functions§
- apply
- Applies the harness’s migrations to the database at
url; withfleetorplan, reconciles the tenants registered in the control database aturlinstead.