Glina

glina config

Invocation

glina config check [--config <path>]
glina config export --out <path> [--config <path>]

glina config --help prints both leaves.

config check

Validate pipeline configuration, enforce the credential-reference policy, resolve role:// values, and check that the selected model backend can be constructed without starting Weles, Blender, or the model service.

  • --config <path> selects the JSON file; otherwise the repository's pipeline.config.json is used.

Reads configuration and resolves credential roles through Stado or the explicitly selected owner-only GLINA_CREDENTIALS_FILE, checks the resolved models.brama or models.openai_compatible settings, recursively replaces resolved secret fields with <resolved: ok>, and prints the redacted config as JSON. It does not rewrite the config or contact the model service.

Missing files, invalid JSON, inline secret values, invalid role references, resolution failures, missing model settings, and unsupported or competing model backends are printed through the CLI envelope as error: <reason> and exit 1. For example, a legacy models.backend or models.openrouter declaration is refused with the supported backend names; replace it with one complete models.brama or models.openai_compatible declaration. A successful secret lookup alone does not mean the model configuration can run.

config export

Create an owner-only resolved configuration handoff for a remote worker.

  • --out <path> is required.
  • --config <path> selects the source JSON; otherwise the repository's pipeline.config.json is used.

Resolves every role:// reference locally, writes JSON with _resolved: true, restricts the file to owner-only access, and prints only {out, resolved:true}. The written file contains secrets, and config check refuses it for that reason.

Refusals

  • glina config without a leaf, or with any leaf other than check and export, writes error: config takes check or export --out <path>; got <the words given> and exits 2.
  • glina config export without --out writes exactly error: config export requires --out <path> and exits 2.
  • Configuration, vault-resolution, write, and chmod errors are printed as error: <message> and exit 1.
  • The retired spellings check-config and export-config are unknown commands and exit 2.