Skip to main content

verdictan regions

verdictan regions lists available regions and shows the region that the CLI uses.

For profile-scoped defaults, use verdictan configure.

Commands​

List published regions​

verdictan regions list
verdictan regions list --json
verdictan regions list --enabled
verdictan regions list --group eu
verdictan regions list --sovereignty-class sovereign

The command lists the regions that the discovery API returns. The output includes locality metadata and API endpoints. Without a token, this uses the public catalog. With a token, it uses the organization region catalog. --group must use authenticated organization metadata. Do not use --enabled with --disabled.

Set the default region for a profile​

verdictan configure set region eu-west --profile default
verdictan configure get region --profile default
verdictan configure list-profiles

This stores the selected region in ~/.verdictan/config.yaml.

Alias: verdictan regions use​

verdictan regions use eu-west --profile default

verdictan regions use writes the same profile-scoped default_region entry.

Alias: switch​

verdictan regions switch us-east --profile default

switch is an alias for use.

Show the resolved region​

verdictan regions current

Use this to see the resolved region and the precedence source.

Show detailed region status​

verdictan regions status

This command shows the status fields from the regions endpoint. It shows gateway count, active-session count, and heartbeat fields when the endpoint gives them.

Per-command override​

For API-backed commands that expose their own region option, put --region on that command:

verdictan events tail --region us-east

The top-level form, verdictan --region us-east ..., is a compatibility shim for local gateway/runtime surfaces that continue to read process-wide region context. It is not the region fallback used by Config::resolve for API-backed commands.

Precedence​

For ordinary API-backed commands, region resolution follows this sequence:

  1. The command's --region <region> option
  2. profiles.<profile>.default_region in ~/.verdictan/config.yaml
  3. the legacy root-level default_region field in the same file

VERDICTAN_REGION is not a fallback in that API-command resolution path.

verdictan regions current is a diagnostic for the older process-wide context. It shows VERDICTAN_REGION first (including a value populated by the top-level verdictan --region shim), then the profile default, then the legacy root-level default. It also prints the independently resolved API endpoint. A region selection does not create or replace that endpoint.

Declarative-config precedence

verdictan regions current shows the CLI-requested region. It does not override the locality in policy-config.yaml for gateway or provider routing. It also does not change the locality from a published hostname.

Region behavior

CLI endpoint selection and provider routing are different. A command's region header does not rewrite VERDICTAN_API_URL. The gateway provider config controls provider fallback behavior, not verdictan regions.

If you do not configure a region, verdictan regions current reports no region configured. API-backed commands can call their configured API endpoint without a region override. The API contract specifies if an operation must use locality.

Next steps​