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
Ansible Collection #545
Comments
+1 for this. |
+1 |
+1 We just stood this up in our lab to evaluate and are planning to move forward shortly. We have forked this project into our internal gitlab, but I agree, this would be much nicer to use/manage if it were a collection... especially if you publish this to the galaxy. |
It probably makes sense to keep #325 for publishing and this one for reformatting the repository. Therefore, the other ticket needs to wait until this one gets in. Aside: Instead of posting "+1"-style comments (which only serve to spam subscribers), please hit the "thumbs up" button at the bottom of the description as this provides useful data on how many folks are interested. Thanks! |
@gcupic Please (re)read the second paragraph of my comment above. Thanks. |
Hello guys, We are working hard to maintain and improve our repositories day by day and we will work on this matter as soon as possible. Thanks for your patience! |
I have been working on turning the 4.3 branch into an ansible collection containing the roles and playbooks. I have tested the all in one deployment and deploying agents and both of those work. https://github.com/atcommander/wazuh I created a pull request 855 |
I'm new to Wazuh and I was very happy to see this official Wazuh Ansible repository! Great work!
It would be nice to enhance this project by aligning it to the Ansible collection format, so one can easily install the playbooks and roles by using the Ansible Galaxy cli-tool. Roles could be accessed by name instead of paths. Adding it to the Ansible Galaxy repository should be considered.
Installation
From galaxy ...
... or from github repo and stable branch
(requires
ansible>=2.10
)Using Roles
The text was updated successfully, but these errors were encountered: