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)
On Tuesday, 5 September 2017 15:51:44 UTC+1, Steve Saner wrote: > > On 09/05/2017 09:04 AM, Ash Powell wrote: > > Thanks for the links. > > > > Watching the video, it mentions about storing the Playbook in a Git > > repo, but nothing about storing the roles in a Git repo. > > > > I'm referring to the files that (by default) sit on > "/etc/ansible/roles/" > > > I, personally, don't store anything under /etc/ansible (other than > /etc/ansible/ansible.cfg). > > I have a directory in my user home that has the following structure: > > ansible/ > - group_vars/ > - hsot_vars/ > - library/ > - roles/ > - inventory > - playlist1.yml > - playlist2.yml > ... > > This whole directory is a git repository and I cd to that directory > before running ansible-playbook. > > So, just like you are suggesting, I can work on the roles or libraries > or playlists on a develeopment machine (my workstation) and then I can > push the repo and pull it down on the production server from which > ansible is normally run. > > I don't know that this is the best way, but it certainly works. > > 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/51b3b25f-e255-4eae-9051-1e19479ff816%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
