-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Release 4.3.6 - Release Candidate 1 - E2E UX tests - GitHub integration #14323
Comments
Environment preparationVagrant file containg the description of the 4 machines using centos
Network configuration 🟡 Because I know Centos 8 comes with firewalls enabled by default in the vagrant box I am using, I have opted for disabling it, instead of implementing the adequate firewall policy for Wazuh. We should consider adding a note to the documentation talking about firewalls and wazuh.
IndexerInstallationSet up pre-release repository
Configuration
Checks
ServerInstall dependencies🟡 When installing dependencies, if you copy & paste the whole block of commands it won't work appropriately, as the first command does not have a -y option. This makes the command ask for user input, so it does not execute the other pasted commands.
Execute the other commands manually:
🟡 Trying to compile Python from source, following the optional instructions does not work, as the package python34 does not exist in Centos 8 latest version. Following the documentation, I've changed to The documentation also say: But I was unable to find when to execute that command to add the PYTHON_SOURCE flag.
Install Wazuh ManagerDownloading the package required an updated URL to use the pre-release
Building wazuh-manager using the provided script
🟡 The script will start the wazuh-manager service by default, but we do not include instructions to check if the service is running. I have modified the command to check if it was running and it was.
Installing other components🟡 The documentation refereces other guide, but it is not clear what steps the user should follow. For example to install filebeat we need to also set up the wazuh repositories. Filebeat installation
AgentFollowing the documentation to install from sources. 🟡 When installing dependencies, if you copy & paste the whole block of commands won't work appropriately, as the first command does not have a -y option. This makes the command ask for user input, so it does not execute the other pasted commands. In this case, the CMake installation is not optional. Built from sources using the provided script. (output elided due to size) Enrolling the agent manually, following the documentation. 🟡 Because the enrollment is separated into two stages, we might want to tell the user to save the key which was just obtained for the next step, right when the key is obtained, in addition to the general process.
DashboardInstallation using the step-by-step guide. I have modified the install commands to use the pre-release packages.
Configuring wazuh-dashboard
Only for distributed deployments
|
GitHub IntegrationSet up trial account
Configure Wazuh Agent
🟡 Our documentation does not show the user how to check if the module is enabled, nor how to diagnose in case there is a problem.
Check results on UIGitHub module after enabling it on the UI settings 🟡 Our documentation does not mention that we need to enable GitHub module on the UI |
Closing as all issues has been reported. |
The following issue aims to run the specified test for the current release candidate, report the results, and open new issues for any encountered errors.
Test information
Test description
Deploy Wazuh with the following design:
Follow the documentation at:
https://documentation-dev.wazuh.com/current/github/index.html
Test different use cases of Github events and see that alerts are generated and make sense.
Test report procedure
All test results must have one of the following statuses:
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause.
An extended report of the test results must be attached as a ZIP or TXT file. Please attach any documents, screenshots, or tables to the issue update with the results. This report can be used by the auditors to dig deeper into any possible failures and details.
Conclusions
All tests have been executed and the results can be found here.
git
value toall
inapi_parameter
in the default configuration shown in the documentationAuditors' validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
The text was updated successfully, but these errors were encountered: