config-startup-validation

Fail-fast startup config validation for TOML files is enforced by applying a validate() method to check mandatory fields like database.dsn and management.port, halting deployment immediately if configurations are invalid.

To add a new required field to config.toml validation, extend the validate() checks, update the validBaseConfig() test helper, and synchronize the TOML fixtures in the config/ directory to maintain test accuracy.

Fail-fast configuration validation during application startup prevents services from running with missing or invalid settings, catching misconfigurations in mandatory fields like database.dsn early through static validation before deployment proceeds.

Yes, config-startup-validation integrates directly with TOML fixtures and test files by validating mandatory fields via the validate() method and ensuring test fixtures in the config/ directory stay synchronized with required fields.

Application startup fails when new required fields are added to TOML config because the fail-fast validation mechanism detects missing mandatory entries, requiring you to update validBaseConfig() and TOML fixtures to pass tests.

Yes, you can use config-startup-validation to check database DSN and management port settings, as it specifically enforces mandatory field validation for these entries within cc-connect's config.toml across tests and static validation.