stado database
Invocation
stado database <COMMAND>Purpose
Resolve fleet databases: placement endpoint and credential coordinate
Required inputs and options
This command has no command-specific inputs or options.
Output and state effect
This command group selects one of the subcommands listed below; use its exact child invocation to perform an operation.
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.
Subcommands
list— List declared databases and whether each is placedresolve— Resolve one database for an authorized consumerdeclare— Declare a database in the Stado configurationcreate— Place a fleet database, create a Supabase project, or declare an existing external serverplace— Place a fleet database on this host: the host-side half of `create --provider fleet`adopt— Bring a declared database's credential item in line with its hosted Supabase projectpush— Make a host's database declarations equal to this machine'sremove— Remove a database declaration from the Stado configurationdestroy— Destroy a database Stado created: the inverse of `create`grant— Grant one or more consumers access to a declared databaserevoke— Revoke one or more consumers' access to a declared databaseclient— Let the database's library client read what `stado_database::connect` reads