-
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
[Remote clusters] Migrate to new ES client #98747
[Remote clusters] Migrate to new ES client #98747
Conversation
@elasticmachine merge upstream |
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
@elasticmachine merge upstream |
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.
Thanks a lot for migrating Remote Clusters, @jloleysens! Code changes LGTM and tested locally 👍
I'll merge and backport this as soon as CI is green again.
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @yuliacech |
* migrate add cluster route and jest tests * migrated delete remote clusters route * migrated the get route * migrated the update route * added shared types file * reduce some test boilerplate * fix type issues introduced by new types from ES client Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* migrate add cluster route and jest tests * migrated delete remote clusters route * migrated the get route * migrated the update route * added shared types file * reduce some test boilerplate * fix type issues introduced by new types from ES client Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
See #73973
Jest test refactor
Server side jest tests were refactored due to the different API exposed by the client. For each test file the steps taken were:
addRemoteClustersTest
and associated interfaceTestOptions
beforeEach
The intention was to make the tests more standardised with the patterns in our other plugins and to not introduce too much additional "test creator" functionality since this can make the tests harder to maintain.
How to test
./.es/8.0.0/bin/elasticsearch -E cluster.name="elasticsearch" -E http.port=9222 -E node.name=node3 -E path.data=/tmp/data -E discovery.type=single-node
localhost:9301
as the seed host for the remote cluster, this should be the default publish port for the second node