CLI reference / database / client

stado database client

Invocation

stado database client [OPTIONS] <NAME>

Purpose

Let the database's library client read what `stado_database::connect` reads. A product opens its database through the `stado-database` crate as the Skarbiec consumer `<name>-database-client`. This widens that consumer's grant on the vault owner to the fields the crate reads: `pooler_url`, plus `ca_certificate` for a server and `session_url` for Postgres. The bearer in the owner's `~/.stado/<name>-database-client-skarbiec-token` is kept, so no host's copy needs syncing again. Running it again changes nothing. A client the vault owner holds no bearer for is refused with Skarbiec's answer.

Required inputs and options

Input or optionContract
<NAME>Positional input; required or optional as shown in the invocation.
--jsonEmit machine-readable output

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.