-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitoring: legacy ES client usages blocking migration of the licensing
plugin
#92185
Comments
Pinging @elastic/kibana-core (Team:Core) |
It'd say it's time to get rid of the legacy wrapper. Monitoring plugin must migrate to the new ES client before @chrisronline @igoristic Is this work planned any time soon? Is it possible to refactor |
@restrry I'm investigating solutions in #93620 |
@restrry #93620 should handle unblocking the license service. We'll do the work to refactor the legacy createClient usage in a separate PR. |
Is there a replacement API we should be using that will accept a
vs
OR should I just update |
@simianhacker should be done in #92143 @pgayvallet any ETA for this? |
There wasn't, but if we're unblocked, I will try to do it asap. Need to take a look to check if #93620 solves all we need to unblock the |
So, I tried to migrate the
licensing
plugin to use the new elasticsearch client (#92143)I'm currently blocked by the
monitoring
plugin usage ofcreateLicensePoller
:createLicensePoller
API from thesetup
method instead of the one fromstart
core.elasticsearch.legacy.createClient
API during itssetup
phase (there is no equivalentsetup
API to create new ES clients)Overall, these two points are causing some huge pain to adapt the call to
licensing.createLicensePoller
, as creating the new ES client frommonitoring
'ssetup
method can no longer be synchronous, meaning that we need to either:licensingService
be created duringstart
(and passed to the routes created duringsetup
via referencelicensingService
receive a promise of an ES client and change its APIs from synchronous to asynchronousMonitoringPlugin.getLegacyShim
(no disrespect, but) atrocities and use request handler context to propagate the monitoring licensing service down to the routes.kibana/x-pack/plugins/monitoring/server/plugin.ts
Lines 102 to 106 in 3b3327d
kibana/x-pack/plugins/monitoring/server/plugin.ts
Lines 108 to 115 in 3b3327d
One workaround to unblock the migration of the licensing plugin to the new ES client could be to add a new deprecated
createLegacyLicensePoller
API that would use aILegacyClusterClient
instead ofIClusterClient
.cc @elastic/stack-monitoring-ui @restrry
The text was updated successfully, but these errors were encountered: