What it is
import-supabase.
Step one of moving a Supabase project onto the harness (issue #658, ADR 0026). It inspects a Supabase project read-only and produces the migration report: every schema object, RLS policy, auth provider, storage bucket, Edge Function and Realtime publication, each classified as automatic, needs work, or a blocker, with the data size and a rough transfer time. fz import supabase inspect is its command-line front end; the dashboard’s Migrate from Supabase button drives the same engine. Native only: it reads Postgres through sqlx and fails to compile on wasm.
From the crate’s own README.
Ports
Database
History
Changelog.
From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 4 versions recorded, newest first. Every published version is on crates.io.
Other
- updated the following local packages: cratefield-core
2 earlier versions 0.1.0 to 0.2.0
Other
- Supabase import: plan.json, bare
fz import supabasedry run,--apply --plandrift check and target extension preflight (#754) - Supabase import: record per-item dispositions (covered/waived) in a file and merge them into the report (#752)
- import-supabase keep the crate version out of the fixture-report snapshot (#786)
- Supabase inspect: drop managed-schema policies, route storage policies to their buckets, flag RLS-on/no-policy tables (#751)
- Supabase import: plan.json, bare
One of 76 crates in the harness, all of them MIT and all of them in one repository.