Module import_users 

fz import supabase users (issue #659, step 2 of ADR 0026): moves a Supabase project’s auth.users into a running venture’s auth-core over the same admin import fz auth import uses (its send_batch, so there is one HTTP path), then records the source-to-account mapping the data step rewrites references through. cratefield-import-supabase’s read_users is the engine; the CLI flags are documented in lib.rs.

Without --apply nothing is written: the server validates every user and reports a verdict, and no mapping row is recorded. --apply writes both and needs --map-db-url-env. Progress and the summary go to stderr; the JSON report (stdout, or --report) holds the counts, the skipped and unmapped ids and the server’s verdict — never an email, a hash, a token or a credentialed URL.

Exit code: non-zero only when the run cannot finish — a refused input, a failed read, batch or mapping write, or drift in the mapping table. A run that completes reporting conflict or invalid exits zero, like fz auth import: those are the server having answered, and the counts print either way.

Structs

UsersArgs

Everything fz import supabase users was given. The field docs are the clap help, in lib.rs.

Functions

run

The refusal an fz without the feature prints: one line naming the install, mirroring import::inspect’s.