Make sure to correctly preserve block for Elasticsearch::Transport::Client #421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Elasticsearch::Client
is a convenience wrapper forElasticsearch::Transport::Client
.Which provides the ability to initialize the client with a block while allowing
to configure the faraday instance directly.
Now, because
Datadog::Contrib::Elasticsearch
monkey patches this behavior,and calls the parent/original
initialize
function (aliased asinitialize_without_datadog
),it however misses to pass in the block, and only sends the arguments.
Which means, using the dd-trace gem in applications which initialize
Elasticsearch::Client
with block becomes risky, as custom faraday configurations are lost.
This PR fixes the issue.