Fix incorrect config validation on SIGHUP

[rudolf]

Summary

Fixes #59494

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility, including a check against IE11

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[rudolf]

This is only called from

kibana/src/core/server/legacy/legacy_service.ts

Line 108 in 6e6325b

this.kbnServer.applyLoggingConfiguration(getLegacyRawConfig(config, pathConfig));

The only difference between this config object and the one we inject when constructing KbnServer is that this one isn't extended by the legacy plugin discovery. So it won't include any plugin config keys, but as this is used only for logging it shouldn't be a problem.

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[rudolf]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: b26974e

History

• 💔 Build #36177 failed 0c49908
• 💔 Build #36149 failed f3c607c

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[joshdover]

That legacy config class is crazy, thanks for tracking this one down.