-
Notifications
You must be signed in to change notification settings - Fork 19
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
Why does this exist? #9
Comments
@tphummel Do you publish all your roles on galaxy? |
@conrado I do not. i think you might be leading me to the answer. ansible-role-manager can pull from the galaxy registry, github, or any remote SCM server? Whereas galaxy only pulls from the galaxy registry? |
I originally did imagine that, but it's not the case. You can install from source control. However version restrictions are limited It also seems, from the code and (future) release notes https://github.com/mirskytech/ansible-role-manager/blob/906a4f5618082268ec63aacfb9b83d242998a0b3/docs/source/releasenotes.rst , there are plans for including support for modules and playbooks, which would be nice as there's no support for any of that from Ansible. Plugins would be great too. I'm surpised less people have hacked away at something like this. Suppose ansible is fairly new, the adoption is still low. More ancient beings probably use CFengine and Salt. I doubt many people are even using |
I've been using ansible for a little while now, but still don't have a good pattern I like for role reuse across projects. It hasn't been a big enough problem to hack on solutions personally. Nor have I really shopped around for possible solutions. |
At the time being, I don't see the advantage of using ansible-role-manager. With ansible-galaxy, I can download my roles from galaxy, public git repos or private git repos. Modules can be embedded in a role. |
@MiLk are you happy with how |
Yes, no problem for the moment. |
What are the differences between this and galaxy? Why would someone choose this over galaxy or something else?
The text was updated successfully, but these errors were encountered: