Skip to content
qibdo qibdo
Theme
Book a demo

Profiles and configuration

The CLI needs to know two things before it can talk to a cluster: where the cluster is, and which organisation you are working in. Both come from configuration, and configuration is organised into profiles.

Profiles

Section titled “Profiles”

A profile is a named set of settings pointing at one cluster. Because every customer operates their own qibdo Cloud cluster, there is no default endpoint: creating a profile requires one.

Terminal window
qibdo config profiles create prod --endpoint qibdo.example:443
qibdo config profiles create local-dev --endpoint localhost:51051 --insecure

Pass --insecure only for a plaintext development or lab cluster. One profile is active at a time, and the active profile supplies the context for every command that does not override it:

Terminal window
qibdo config profiles activate prod
qibdo config profiles list

A single command can borrow another profile without switching the active one:

Terminal window
qibdo taxonomy workspaces list --profile local-dev

Where a value comes from

Section titled “Where a value comes from”

Every setting is resolved through the same chain, most specific first:

  1. a flag on the command
  2. an environment variable
  3. the active profile (or the one named by --profile)
  4. the built-in default

That is why --endpoint on a single command works without touching the profile, and why a value set on a profile still yields to a flag.

Two commands make the chain visible. qibdo config get prints the resolved value of one key, and qibdo config list prints them all. Adding the global --verbose flag to list shows where each value came from, which is the quickest way to answer “why is it talking to that cluster”:

Terminal window
qibdo config get organisation
qibdo config list --verbose

Writes go to the active profile, and the value is validated before it is stored:

Terminal window
qibdo config set organisation 40b8e818-c052-43f0-8cab-e92cfc1c6f60

Choosing an organisation

Section titled “Choosing an organisation”

Most resources live inside an organisation. Rather than passing --organisation on every command, set it once on the profile and let the chain resolve it:

Terminal window
qibdo config set organisation 40b8e818-c052-43f0-8cab-e92cfc1c6f60
qibdo taxonomy workspaces list

The flag still wins when you need to reach across:

Terminal window
qibdo taxonomy workspaces list --organisation 8f2b1c04-9d33-4a71-b6e2-1f0c5a7d4e19
Section titled “Related”