Config validation should occur up front #20303
Labels
Feature:New Platform
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
In
kbn-core
today, config validation only occurs when the config is needed (e.g. when using the http-related configurations in the http service. This can result in unreliable behaviors for validation in different situations.For example, if you are using the BasePathProxy and an invalid configuration that gets flagged by the new platform config (e.g.
server.maxPayloadBytes: -1000
), the CLI exits almost immediately with the appropriate error message. However, if you do not use the BasePathProxy with that same configuration, then the server starts up fine and then fatal errors a little bit later, which causes a log entry but the process keeps running.We should validate config consistently, and the ideal behavior is to exit the process with an error message ASAP.
The text was updated successfully, but these errors were encountered: