sabaoth config - SabaothCloud

Shows the credential source, the selected organization and the organizations stored on this machine. It makes no network call and needs no credential, so it works before you have logged in.

sabaoth config [--json]

Flags

boolean

default:"false"

Print the result as JSON on stdout.

Output

$ sabaoth config
Config file:       /Users/you/Library/Application Support/sabaoth/context.json
Schema version:    1
Credential source: local context
Selected org:      org_abc

Organizations:
  * org_abc  Acme
    org_xyz  Side Project

The selected organization is marked *. When SABAOTH_API_KEY is set, Credential source reads SABAOTH_API_KEY (saved selection ignored). With --json:

{
  "schema_version": 1,
  "config_file": "/Users/you/Library/Application Support/sabaoth/context.json",
  "credential_source": "local",
  "selected_organization_id": "org_abc",
  "organizations": [
    { "id": "org_abc", "display_name": "Acme", "selected": true },
    { "id": "org_xyz", "display_name": "Side Project", "selected": false }
  ]
}

Field	Description
`schema_version`	Version of the context file format.
`config_file`	Full path of the context file on this machine.
`credential_source`	`local` when the saved login is used (the human output says `local context`, and the key comes from the OS keychain), `environment` when `SABAOTH_API_KEY` is set.
`selected_organization_id`	The selected organization, or `null` if none is selected.
`organizations`	Every organization stored on this machine, with `selected` marking the current one.

Behavior

Never prints a key, in either output mode.
Doesn’t check anything with the server. It shows what’s stored locally. A listed organization may have a revoked key; sabaoth org use and other commands will find that out.
When SABAOTH_API_KEY is set, other commands ignore the saved selection. config still shows it, so you can see what would be used once the variable is unset.