Although building an elastic client for an ESS cluster is possible, the nodes must be configured manually (i.e., nodesSelector). The cloudId property provided by ESS has information about it, so that it's easier just to provide apiKey, apiSecret and cloudId to have a working client.
In a project, I've implemented an extension method for that. If you agree, I can submit the code.
Why is this needed?
Simplify the code
How do you think it should be done?
Already been implemented as an extension function, but it also could be implemented as a new KtorRestClient constructor
Describe the enhancement
Although building an elastic client for an ESS cluster is possible, the nodes must be configured manually (i.e.,
nodesSelector
). ThecloudId
property provided by ESS has information about it, so that it's easier just to provideapiKey
,apiSecret
andcloudId
to have a working client.In a project, I've implemented an extension method for that. If you agree, I can submit the code.
Why is this needed?
Simplify the code
How do you think it should be done?
Already been implemented as an extension function, but it also could be implemented as a new
KtorRestClient
constructorWill you be able to help with a pull request?
Yes!