-
Notifications
You must be signed in to change notification settings - Fork 196
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
Update Wazuh API Installation #326
Comments
Working Branch: feature-326-wazuh-api-installation |
Hi all! We reformulated the tasks so we follow the latest documentation from Wazuh. Changes can be resumed as:
wazuh-ansible/roles/wazuh/ansible-wazuh-manager/tasks/Debian.yml Lines 41 to 49 in 686c02b
wazuh-ansible/roles/wazuh/ansible-wazuh-manager/tasks/RedHat.yml Lines 6 to 25 in 686c02b
Kr, Rshad |
Hi all! After getting a first valid version of the requested configuration, we thought about having a more efficient and better designed Ansible configuration. This improvement is based on the implementation of the following 3 points: 1- Try to use Ansible modules instead of some alternatives like (shell: curl ....) Tasks To do so, we added the following configuration.
wazuh-ansible/roles/wazuh/ansible-wazuh-manager/tasks/main.yml Lines 30 to 36 in 565a84c
Variables As you can see in the task "Download NodeJS repository script" wazuh-ansible/roles/wazuh/ansible-wazuh-manager/tasks/main.yml Lines 17 to 22 in 565a84c
We use a dictionary We added the definition of wazuh-ansible/roles/wazuh/ansible-wazuh-manager/defaults/main.yml Lines 329 to 331 in 565a84c
Kr, Rshad |
Hi all,
The Wazuh API installation is currently done with:
wazuh-ansible/roles/wazuh/ansible-wazuh-manager/tasks/RedHat.yml
Lines 2 to 11 in c2ae0bf
Which is currently outdated. It's required to update it according to the Wazuh Documentation
Tasks:
Update API tasks for RedHat and Debian families
Update conditionals and remove
AmazonLinux | Get Nodejs
taskTest installation on both OS families and ensure API is correctly installed
Best regards
Jose
The text was updated successfully, but these errors were encountered: