worker.yaml is the primary runtime configuration file. It defines environment variables, secret references, and opt-in runtime output used inside the worker container.
Use this when you need to:
- Define runtime environment variables.
- Reference secrets that should be resolved at startup.
- Override defaults at runtime without rebuilding images.
- Runtime-only config:
/home/udx/.config/worker/worker.yaml. - Deployment env vars override
worker.yamlvalues. - Secret reference behavior is documented in
docs/secrets.md. - Provider authentication is not configured in
worker.yaml.
kind: workerConfig
version: udx.io/worker-v1/config
config:
env:
APP_MODE: "worker"
AWS_REGION: "us-west-2"
secrets:
DB_PASSWORD: "aws/db-password/us-west-2"
API_KEY: "azure/kv-prod/api-key"kind: workerConfig
version: udx.io/worker-v1/config
config:
env:
API_KEY: "dev-only-static-key"
secrets:
DB_PASSWORD: "azure/kv-prod/db-password"API_KEY is injected as-is. DB_PASSWORD is resolved from the provider after auth exists and then exported as an environment variable.
- Deployment environment variables (highest priority)
- Deployment environment variables containing secret references (resolved at startup)
worker.yamlconfig.secretsworker.yamlconfig.env
Example override:
# worker.yaml (production defaults)
config:
secrets:
ES_PASSWORD: "gcp/prod-project/es-password"Deployment override example:
docker run --rm \
-e ES_PASSWORD="gcp/staging-project/es-password" \
usabilitydynamics/udx-worker:latest- Storing plaintext secrets in
worker.yaml. - Putting cloud login/session setup in
worker.yaml. - Forgetting that deployment env vars override runtime config.
By default the worker does not print runtime config details. Set WORKER_RUNTIME_OUTPUT=true to emit the redacted runtime contract JSON on stdout.
See docs/runtime-output.md for the output contract, capture examples, and CI artifact usage.
docs/services.mddocs/secrets.mddocs/deployment.mddocs/runtime-output.md