Config validation should occur up front

[epixa]

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.

[epixa]

@elastic/kibana-platform

[azasypkin]

I tried various ideas, none was ideal, but I believe it should be fixed "automatically" or will require relatively simple change once #19994 is merged.

[epixa]

@azasypkin Did #22190 address this?

[azasypkin]

@azasypkin Did #22190 address this?

Nope, but we handle this much better now, i.e. which causes a log entry but the process keeps running shouldn't happen anymore irrespective to the fact where config validation failed (in the core or in the legacy Kibana).

[mshustov]

closed in #35453