Skip to content
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

Upload wazuh-ansible roles to Ansible Galaxy #325

Open
rshad opened this issue Nov 15, 2019 · 5 comments
Open

Upload wazuh-ansible roles to Ansible Galaxy #325

rshad opened this issue Nov 15, 2019 · 5 comments

Comments

@rshad
Copy link
Contributor

rshad commented Nov 15, 2019

Hi all!

It's recommended to always have an organization Ansible roles uploaded to Ansible Galaxy, which provides more popularity and easier way for roles downloading.

So in this issue, we pretend to upload the wazuh-ansible roles to Ansible Galaxy.

Kr,

Rshad

@rshad
Copy link
Contributor Author

rshad commented Jan 21, 2020

Hi all!

We created a Namespace request for wazuh organization on Ansible Galaxy.

ansible/galaxy#2203

Kr,

Rshad

@redgryphon
Copy link

Any update on when the roles will be uploaded on Ansible Galaxy?

@rshad rshad removed their assignment Mar 30, 2021
@rshad
Copy link
Contributor Author

rshad commented Mar 30, 2021

Hi,

Unfortunately, I'm not working on this issue anymore, probably, the @wazuh team would take care of it.

Kind regards,

@colans
Copy link

colans commented Oct 14, 2021

As per #545, it would be best if the repository were formatted as a single Collection, not multiple Roles. Instead of merging these issues, it probably makes sense to keep this one for publishing, and the other one for reformatting the repository, which would need to be done first.

Would it be possible to postpone this one on the other one?

@colans
Copy link

colans commented Oct 15, 2021

I forgot to add that not having this repository published on Galaxy is a serious UX problem. I looked there first, didn't see much (and nothing official) so I wrote my own playbooks. Only later did I discover that this repository exists by accidentally tripping over a mention of it in the documentation. If you'd like to make life easier for folks to start using this product, I'd recommend publishing it there post-haste.

At the very least, it would be nice to link to this from the Unattended installation, as that what I read first (and converted to a playbook). Or at least link from there to the Deployment section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants