If I recall from the talk, the suggestion was each role would have a git repo of its own, then required roles are loaded using a requirements.yml file Some talk about this pattern here: https://stackoverflow.com/questions/25230376/how-to-automatically-install-ansible-galaxy-roles
We don't have lots of people updating roles at the moment so we have all ansible config in a single source code repo and users pull and update their local copies. As noted you have to change ansible.cfg to pick up roles, library and plugins from relative paths but it works ok for us. On Tuesday, September 5, 2017 at 4:50:57 PM UTC+1, Steve Saner wrote: > > On 09/05/2017 10:33 AM, Ash Powell wrote: > > I'm not sure that this would work for us as we might have multiple > > people using/running the same role so it would need to be a common > > location (ie not a home folder) > > In my case I really only have one or two people that would be running > ansible, but I have things set up on a role account, so that anyone that > needs to would log into the same account. > > Another option, I suppose, would be to include a Makefile or something > that "installs" your roles from the git repo to /etc/ansible. > > But really, there wouldn't be anything fundamentally wrong with > /etc/ansible/roles itself being a git repository, probably. > > Steve > > -- > -------------------------------------------------------------------------- > Steven Saner <[email protected] <javascript:>> KD0IJP > Andover, Kansas USA > -- 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/88937761-ce58-4f07-972e-786e6fc9a1d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
