Configuration

Keep environment settings explicit and separate sensitive values from manifests.

Configuration precedence#

Explicit command flags take priority over environment variables. Environment variables override the active context, which overrides user defaults. This makes automation predictable without changing a developer’s saved context.

Setting	Environment variable	Default
Control-plane URL	`DU_ENDPOINT`	Organization-defined
Context name	`DU_CONTEXT`	Active local context
Request timeout	`DU_TIMEOUT`	`30s`
Output format	`DU_OUTPUT`	`table`

Project configuration#

project: catalog
environment: staging
defaults:
  region: eu-central
  labels:
    team: commerce
    cost-center: product
deployment:
  timeout: 300s
  requireApproval: true

Labels are inherited by newly created resources. Changing a default does not silently move existing workloads between regions.

Reference secrets#

Use a secret reference such as secret://catalog/database-url in a service manifest. The runtime resolves the reference using the service identity. Keep actual secret values out of source control and CLI arguments.