-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to support moved filebeat modules #9432
Merged
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
jsoriano
added
enhancement
module
discuss
Issue needs further discussion.
review
Filebeat
Filebeat
needs tests
Team:Integrations
Label for the Integrations team
labels
Dec 7, 2018
Pinging @elastic/infrastructure |
If a module needs to be moved, existing configuration will stop working, this change adds an option to mark an old module as moved to other name. This is being considered for the movement of apache2 module to apache to be coherent with metricbeat module (elastic#9402).
jsoriano
force-pushed
the
filebeat-move-modules
branch
from
December 7, 2018 11:12
be2f921
to
30bc249
Compare
ruflin
reviewed
Dec 7, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add some tests to this PR? Not sure yet what the best way would be here.
Test added with a dummy modules directory for this case. |
jenkins, test this |
ruflin
approved these changes
Dec 12, 2018
jsoriano
added a commit
that referenced
this pull request
Jan 12, 2019
Rename filebeat `apache2` module to `apache`. `apache2` module is kept as a "moved" module (#9432) so existing configurations continue working. Aliases for renamed fields are added and they will be handled as fields renamed for ECS.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
discuss
Issue needs further discussion.
enhancement
Filebeat
Filebeat
module
review
Team:Integrations
Label for the Integrations team
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.
If a module needs to be moved, existing configuration will stop working,
this change adds an option to mark an old module as moved to other name.
This is being considered for the movement of apache2 module to apache to
be coherent with metricbeat module (#9402).
So if the
module.yml
file of the apache2 module contains:Every time the
apache2
module is used a warning is printed about thechange and
apache
module is used instead.