--json- Machine-readable output on every command. Human tables are the default.
Exit codes- 0 ok · 1 error · 2 usage · 3 permission or auth denied. Branch on them in scripts and CI.
--profile <name>- Names the tenant on every command (no default profile since 0.5.7). Set DLAKE_PROFILE once per shell session instead.
@file.json- Read any argument from a file. The reliable form on Windows, where quoted JSON is mangled by the shell. @@ passes a literal leading @.
JSON arguments- A value starting with [ or { is sent as JSON; a plain comma list still works for arrays of scalars.
--confirm true- Required by destructive tools such as restart_dab and drop_table; the command stops before doing anything if it is missing.
--help everywhere- Every command prints its help without a profile. For dlake admin <tool> --help and dlake tool <tool> --help, the tool's live argument schema comes from the MCP host, so it is shown when a profile is given; without one you get the generic help for the verb.
--field Name=Value- On dlake admin, a tool with a single object argument (such as a wizard step's fields) takes a repeated --field, each setting one value over the --fields JSON. Name=@path reads the value from a file. In PowerShell, quote @file values: a bare leading @ is the splatting operator.
Secrets- Prefer DLAKE_API_KEY or --api-key-stdin over --api-key on the command line, which leaks to shell history. Passwords are prompted hidden or piped with --password-stdin; a plain --password flag is refused.