[galaxy] Avoid broken dependencies - fork+git submodule vs Galaxy+TRUST

Archives Ansible Project
1

Hi Guys,

I’m kinda junior DevOps guy at my company and I’m learning quite a lot these days about Ansible and how to manage git projects on my own.

So, here is what I’m thinking about. What happens if the user, who’s role my playbook depends on, decides to remove his repository?

Here is what I’ve done. I’m working behind a proxy and we have our own private GitHub Enterprise server behind that proxy. I’ve cloned the repo to our instance of GitHub (we don’t have a public company account and I did not want to use my own public one), and added that private fork as a git submodule to my project. That seemed like a reasonable approach, then I realized I could possibly use ‘ansible-galaxy install -f my_deps_with_private_github_links.yml’.

What would be a good way? If I’m using many roles from one specific GitHub user and he or she decides to move away from GitHub that could cause quite a harm. So should I clone everything which is extra work or should I trust the repo will still exist even one or more years later? If I know correctly, Galaxy does not store anything, the source is totally from GitHub.

Thanks is advance.

Cheers,
Ferenc

2

Hi,
if I understand it well, you don’t want to be dependent on user name/existance on Github while you are using roles from your internal Github Enterprise.

There is way how to solve this. You could have all roles not filed under user, but under organization – https://help.github.com/enterprise/2.5/admin/guides/user-management/organizations-and-teams/

Example:
On Github i have username roolo and here is my role for Ansible – https://github.com/rooland-provisioning/ansible-role-vim-machine . So when I’ll eventually leave Github, this role will be still available for other people

Dne pondělí 21. září 2015 14:36:33 UTC+2 Ferenc Szabo napsal(a):