> > Unclear of how inventory and example playbooks are related. >
In a lot of cases the playbook itself is always the same except for the name of the role. I have around 20 roles on the galaxy and pretty much all of them have an identical playbook in the example. The thing that changes is overwriting or defining a few variables in your inventory. Like "here's the bare minimum to get rolling with the role", rather than just show someone 50 default variables up front. That is where the inventory name comes into play. I consider group_vars/etc. as part of my inventory. I'd like to see an attempt at not bifurcating the tooling here. > I wanted to merge some of this into core if you guys felt it was reasonable but the ansible-galaxy script is untouchable IMO. It is already massive with a bunch of mixed concerns. I don't think it can sustain me dropping in 1k+ lines of python without it exploding and to keep it all broken up would have required coming up with my own directory structure which is fine for my project but I wasn't sure that would fly over well with ansible. What parts do you like and don't like? How much of it wouldn't ever get into core? Would ansible-galaxy need to be renamed? -- 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/2ed77b14-bf13-4151-9e5a-e83643f12639%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
