Good intentions aside, that librarian project should not needed to be
created - there's somewhat of a tragedy of the commons effect from github
where not everyone joins the lists and knows about the work we are all
trying to build here, coupled with a bit of a simple name problem that led
people to assume ansible-galaxy was only for galaxy.ansible.com, when that
wasn't the case - it's really the role tool for the whole "galaxy" of
ansible modules, or whatever.

Ansible's always been a "batteries included" kind of ecosystem, where we
want everybody to collaborate on shared tooling, rather than have 5
ecosystem projects spring up that all work differently, and lack the
critical mass.

It's the same reason we have the 235-ish modules in core, rather than the
40-60 of some other projects - so you have to hunt less around distributed
projects and find that some do some things and others do other things.

I particularly don't like how that tool creates another syntax for
describing things, worse yet one that looks like Ruby in a system of
software where that doesn't /quite/ make sense, but it also didn't quite
make sense that a simple list of roles needed to be in YAML just yet either.

So it may be in the future we support both a YAML format and the existing
string format, TBD.

In any event, I regret that no list discussion occured when that tool came
onto the scene, as I think a lot of those contributions could have been
funneled into the shared project.






On Wed, Aug 13, 2014 at 10:20 AM, Sam Doran <[email protected]> wrote:

> I would love to have this functionality added to ansible-galaxy. I'm
> currently using librarian-ansible
> <https://github.com/bcoe/librarian-ansible>because it allows me to
> specify my own git repos for sourcing roles. I don't care for how
> heavy-handed librarian-ansible is, though: each time I run any
> librarian-ansible command it wipes out all changes in the librarian_roles
> directory, causing all my customizations to be lost. I much prefer the
> behavior of ansible-galaxy but can't use it because I host my roles on a
> private git repository.
>
> One thing I do like very much about librarian-ansible is the
> syntax/capability of the Ansiblefile:
>
> # This will pull a role using the Ansible Galaxy API
> role "kunik.deploy-upstart-scripts"
>
> # This allows me to specify my own git repository as a source as well as a
> version number
> role "disa-stig-rhel6", git: "[email protected]:
> ansible/role-disa-stig-rhel6.git", "1.0"
>
> # I can also point to github repos
> role "role "pgolm.ansible-playbook-monit", github: "pgolm/ansible-playbook
> -monit"
>
>
> There are philosophical differences in how the two tools operate as well.
> With librarian-ansible, you are not meant to ever customize roles under
> the control of librarian-ansible. This makes keeping the roles up to date
> rather easy but customizing them is not recommended since any changes will
> be lost (unless you copy the role out of the librarian_roles folder,
> essentially forking the role).
>
> ansible-galaxy, on the other hand, lends itself more to using shared
> roles as a starting point and not as an ongoing source of truth. I could be
> using ansible-galaxy wrong, but that's how I see it (or maybe it's
> flexible enough to be used either way). I run ansible-galaxy once to get
> the role, then customize it to my liking. Running ansible-galaxy again
> does not overwrite any customizations I have made to the role, which is
> much friendlier and more in line with how I like to use the tool.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/cc0614f4-4d5a-4f74-97d3-42de785bc445%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/cc0614f4-4d5a-4f74-97d3-42de785bc445%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgwm%3Dcuz7vpSYvkgG3BDjAHT0cCn5cyJdtum%2B2s5h9_WJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to