Configuration commands

Run these against a compiled schema module in your application. Decorated TypeScript schema files require an appropriate loader; compiling to ESM first avoids depending on a source loader in deployment.

npx --no-install udiot config validate --schema ./dist/config/schema.js --env production
npx --no-install udiot config diff --schema ./dist/config/schema.js --env production
npx --no-install udiot config scaffold --schema ./dist/config/schema.js --env staging --with-docs
npx --no-install udiot config trace database.host --schema ./dist/config/schema.js --env production

All four commands require --schema and --env. trace takes the key as a positional argument, not --key.

• validate: --config-dir, --manifest.
• diff: also --compare-file and --compare-from.
• scaffold: --config-dir, --with-docs, --force.
• trace: --config-dir, --manifest.

Scaffolding writes files; review existing configuration before using --force. Use secret providers for credentials and do not commit generated secret values. See configuration and programmatic tooling.