-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
migrate es version check to new client #71215
migrate es version check to new client #71215
Conversation
Pinging @elastic/kibana-platform (Team:Platform) |
internalClient.nodes.info.mockReturnValueOnce([ | ||
{ body: createNodes('5.1.0', '5.2.0', '5.0.0') }, | ||
]); | ||
// @ts-expect-error we need to return an incompatible type to use the testScheduler here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this problem be solved when we switch to a client generated for Kibana?elastic/elasticsearch-js#1239
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately no, this is the 'cannot use promises with marble scheduler' issue where we return an observable or a plain value instead of a promise to be used with rx.of
. We just did not have the TS error with the legacy client because the mock was not correctly typed.
…client-version-checl
…client-version-checl
💚 Build SucceededBuild metricsmiscellaneous assets size
History
To update your PR or re-run it, just comment with: |
Summary
Part of #35508
Migrate the ES version check to use the new ES client instead of the legacy one.
Note: this is targeting
7.10
and should not be merged / backported to7.9
Checklist