-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Test Kibana Platform plugins cannot use @kbn/config-schema #61652
Copy link
Copy link
Closed
Labels
Feature:New PlatformTeam:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Team:OperationsKibana-Operations TeamKibana-Operations TeambugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
Metadata
Metadata
Assignees
Labels
Feature:New PlatformTeam:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Team:OperationsKibana-Operations TeamKibana-Operations TeambugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
Type
Fields
Give feedbackNo fields configured for issues without a type.
In #61614 we started to migrate fixture plugins we use in API integration tests to the New Platform, everything works fine locally, but not on this CI. These plugins define routes with validation based on the
@kbn/config-schemaand when these used with the Kibana built for integration tests on CI, Kibana fails to start with the following error:Most likely the
instanceofcheck here fails because "Type" that plugin creates isn't the same as expected by the Core (I think we had something similar with RxJS package in the past).You can use #61614 to reproduce the issue (without last commit with a workaround that removed
@kbn/config-schemadependency from test plugins entirely).I'm tagging both Platform and Operations since it's not exactly clear what the root cause is.