ConfigService wrongly marks unknown config paths as handled #36423
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:New Platform
low
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Kibana wrongly marks unknown config paths as handled if it has a string intersection with any correctly declared path.
Steps to reproduce
kibana.yml
declares config for a pathplugins.myvalueA
pluginA
declares its configPath asplugins.myvalue
Expected outcome
Kibana fails, as
kibana.yml
contains unknown configuration valueplugins.myvalueA
Actual outcome
Kibana works, because
plugins.myvalueA
is marked as handled bypluginA
due to checks:We should match the path segment, not just check a string inclusion.
The text was updated successfully, but these errors were encountered: