-
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
Move generator packages of Filebeat from scripts/generator to generator #9147
Move generator packages of Filebeat from scripts/generator to generator #9147
Conversation
I assume as soon as #9097 is merged, this Diff becomes much smaller? |
Yes. And it also needs a rebase. |
6d36ba5
to
bcaf493
Compare
bcaf493
to
07d7801
Compare
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.
LGTM, add an entry to CHANGELOG-developper.asciidoc
I've built this PR locally and create a few module/fileset, and they are the same as before.
Previously green. I only added a changelog entry. |
This PR exposes the existing Filebeat module generators as `generate` subcommand. ``` $ ./filebeat generate -h Generate Filebeat modules, filesets and fields.yml Usage: filebeat generate [command] Available Commands: fields Generates a new fields.yml file for fileset fileset Generates a new fileset module Generates a new module ``` The subcommands `module`, `fileset` and `fields` use the same code as the scripts. I added E2E tests to validate the functionality. Blocked by #9147 as it contains the refactorings of that PR.
From now on generator functions are located under
generator
package.This PR is the reincarnation of #7506 It includes the refactoring requested previously.