Added the modifications for file md5 validation for logstash extended file plugin #83
Conversation
This file contains hidden or 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
1 participant
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.
I have created an extension to the default logstash file input plugin. The purpose of the extension is validate the MD5 hash of any new file by calling an endpoint whenever a new file event is observed.
I have explained how I have handled it here: elastic/logstash#6895
I have added the changes to allow additional config parameters in the logstash plugin and made the md5 digest calculation related changes in this filewatch repo. My changes will only run if the auth-endpoint parameters is found in the @watcher object which is created to subscribe for file event. If not the usual flow will be taken.