Fixes overwrite of ES options #140
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
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.
Proposed changes
Currently, logger.go overwrites most user provided CLI ElasticSearch options. To test set "-elastic-ssl", "-elastic-username", or "-elastic-password" and notice these are not sent to the ElasticSearch cluster. The issue is on line 52-55 of logger.go which take in two user provided options but ignore the rest. This PR fixes that by including all supplied ES options. This behaved correctly on a ES server I tested against.
Checklist
I am not sure how to run the checks. Any help with that would be great. Thank you!