CLI 0.1.0
On this page
Related contents
Released .
ScopeDB CLI 0.1.0 is available in public preview. Use it to explore a workspace, run queries in scripts, and review Catalog changes before applying them. See the CLI guide for installation and everyday commands.
What's new
- Approve a personal login in ScopeDB Console through a browser callback or device code. Credentials renew automatically and use the OS keyring when available, with a visible plaintext fallback warning.
- Export Catalog definitions, preview replacement changes, and apply a reviewed plan with version and connection checks.
- Read queries from a file or stdin and write table, JSON, JSON Lines, or CSV results to stdout.
- Check query access with
scope doctorand use explicit timeouts when a command must stop waiting.
Upgrade from a release candidate
Install 0.1.0 using the release archive or Go source, then confirm it with scope version. When upgrading from an earlier release candidate, sign in again with scope auth login. Login now uses Console approval; the old email/code flags and browser-session credentials are no longer used.
Update scripts that use the previous commands and flags:
| Earlier command or option | Use in 0.1.0 |
|---|---|
scope login, logout, status | scope auth login, scope auth logout, scope auth status |
scope workspace show | scope workspace get |
scope open [page] | scope console [page] --open |
scope open [page] --print | scope console [page] |
-f <format> | --format <format>; -f now selects an input file |
scope query --output results.csv | scope query -f report.scopeql --format csv > results.csv |
Query --force | Shell redirection controls overwriting |
Login --email and --code | Browser approval, or --use-device-code for another device |
The old command paths are not aliases. scope console always prints its URL; only --open launches a browser. Queries now wait without an additional client-side limit by default. Use --timeout 5m to retain the earlier wait limit, and review query output handling before replacing output flags with redirection.
For JSON consumers, scope auth status uses credential_source instead of auth_mode and email instead of user, and adds refresh_token_expires_at. Read provisioning.status from scope workspace get --format json instead of the old status response's provisioning_state. Workspace JSON uses connection.endpoint instead of connection.api_base_url. Successful scope auth login --format json reports the signed-in account and selected workspace.
Workspace selection is local to the current CLI login. Existing credentials are discovered automatically; credential_store in config.toml and SCOPEDB_CREDENTIAL_STORE no longer select a backend. Follow Credential storage and logout to inspect or change the current login's storage.