Allow for TLS connections to ElasticSearch #1398
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
June 22, 2016 07:55
Extremely similar implementation to the HTTP JSON module's implementation of the same code.
mglazer
force-pushed
the
feature/ssl-elasticsearch
branch
from
eec26c5
to
66cbf3e
Compare
|
thanks @mglazer ! |
chebrolus
pushed a commit
to chebrolus/telegraf
that referenced
this pull request
Jun 24, 2016
* Allow for TLS connections to ElasticSearch Extremely similar implementation to the HTTP JSON module's implementation of the same code. * Changelog update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Required for all PRs:
Extremely similar implementation to the HTTP JSON module's
implementation of the same code.