Fixed wrong input and output file #164
Merged
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
The file /etc/logstash/conf.d/ansible-input/input.conf contained an OUTPUT, while /etc/logstash/conf.d/ansible-input/output.conf contained an INPUT. Fixed that
…/ansible-collection-elasticstack into fix/twisted-input-output
|
Thank you! (Don't mind the failing linters - we need #160 to be merged to fix this issue. It's basically a newly introduced linter role for |
…elasticstack into fix/twisted-input-output
ivareri
pushed a commit
to ivareri/ansible-collection-elasticstack
that referenced
this pull request
Jun 17, 2025
The file /etc/logstash/conf.d/ansible-input/input.conf contained an OUTPUT, while /etc/logstash/conf.d/ansible-input/output.conf contained an INPUT. Fixed that
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The file /etc/logstash/conf.d/ansible-input/input.conf contained an OUTPUT, while /etc/logstash/conf.d/ansible-input/output.conf contained an INPUT. Fixed that