-
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
Test Filebeat modules from packages #7488
Labels
Comments
This also applies to Metricbeat modules. |
andrewkroh
added a commit
to andrewkroh/beats-tester
that referenced
this issue
Aug 27, 2018
Test that the `filebeat modules list` and `metricbeat modules list` commands are working. Relates elastic/beats#7488 elastic/beats#8105
andrewkroh
added a commit
to andrewkroh/beats-tester
that referenced
this issue
Aug 27, 2018
Test that the `filebeat modules list` and `metricbeat modules list` commands are working. Relates elastic/beats#7488 elastic/beats#8105
I opened elastic/beats-tester#87 which runs both filebeat and |
ruflin
pushed a commit
that referenced
this issue
Aug 28, 2018
This change ensures that `modules` (Filebeat) and `modules.d` (Filebeat & Metricbeat) folders contain files in the right place. Permissions and ownership were already tested Part of #7488
exekias
added a commit
to exekias/beats
that referenced
this issue
Aug 28, 2018
…stic#8107) This change ensures that `modules` (Filebeat) and `modules.d` (Filebeat & Metricbeat) folders contain files in the right place. Permissions and ownership were already tested Part of elastic#7488 (cherry picked from commit aa6c76e)
exekias
added a commit
to exekias/beats
that referenced
this issue
Aug 29, 2018
…stic#8107) This change ensures that `modules` (Filebeat) and `modules.d` (Filebeat & Metricbeat) folders contain files in the right place. Permissions and ownership were already tested Part of elastic#7488 (cherry picked from commit aa6c76e)
andrewkroh
added a commit
to elastic/beats-tester
that referenced
this issue
Aug 29, 2018
Test that the `filebeat modules list` and `metricbeat modules list` commands are working. Relates elastic/beats#7488 elastic/beats#8105
exekias
added a commit
that referenced
this issue
Aug 30, 2018
…in resulting packages (#8111) * Test modules and modules.d folder contents in resulting packages (#8107) This change ensures that `modules` (Filebeat) and `modules.d` (Filebeat & Metricbeat) folders contain files in the right place. Permissions and ownership were already tested Part of #7488 (cherry picked from commit aa6c76e)
exekias
added a commit
that referenced
this issue
Aug 30, 2018
…in resulting packages (#8136) * Test modules and modules.d folder contents in resulting packages (#8107) This change ensures that `modules` (Filebeat) and `modules.d` (Filebeat & Metricbeat) folders contain files in the right place. Permissions and ownership were already tested Part of #7488 (cherry picked from commit aa6c76e)
I guess this one can be closed now @andrewkroh ? |
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
…ntents in resulting packages (elastic#8136) * Test modules and modules.d folder contents in resulting packages (elastic#8107) This change ensures that `modules` (Filebeat) and `modules.d` (Filebeat & Metricbeat) folders contain files in the right place. Permissions and ownership were already tested Part of elastic#7488 (cherry picked from commit 5577137)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We don't have any tests in place to detect if the Filebeat modules work from the packages we produce. I noticed this because they weren't included in the packages and none of our tests failed. I suggest adding some tests in these areas:
Check that packages have
modules
andmodules.d
at a minimum. Currently we check file permissions and ownership, but we don't assert they exist. I suggest adding a flag like--modules
or--dir
to package_test.go that causes the check to test that the directories exist in all packages.Run some tests on the Filebeat modules from beats-tester. Maybe execute the enable commands.
Test filebeat/metricbeat modules list beats-tester#87
The text was updated successfully, but these errors were encountered: