There are some important distinctions to be made here …
-
Roles in the “elan” namespace are linked to the “elan” provider namespace, which is owned by two users currently ikiesow&tibroc …
elan legacy namespace
elan provider namespace -
The installs were fixed a few days ago by patches we rolled out to production and some scripted cleanup on duplicate roles …
[jtanner@p1 tmp]$ rm -rf ~/.ansible /tmp/roles ; ansible-galaxy install -p roles elan.opencast_user
Starting galaxy role install process
- downloading role 'opencast_user', owned by elan
- downloading role from https://github.com/elan-ev/opencast_user/archive/main.tar.gz
- extracting elan.opencast_user to /tmp/roles/elan.opencast_user
- elan.opencast_user (main) was installed successfully
- The “elan” namespaces are not in fact pointing at elan (Elan Feingold) · GitHub nor are they owned by that github user. The problem is a bug in the galaxy backend that assembles the avatar url in a very naive way…
return {
'dependencies': dependencies,
'namespace': {
'id': obj.namespace.id,
'name': obj.namespace.name,
'avatar_url': f'https://github.com/{obj.namespace.name}.png'
},
'provider_namespace': provider_ns,
'repository': repository,
'tags': tags,
'versions': versions
}
That url needs to come from the provider namespace’s metadata instead …
[jtanner@p1 tmp]$ curl -s -L http://galaxy.ansible.com/api/v3/namespaces/?name=elan | jq .data[].avatar_url
"https://avatars.githubusercontent.com/u/1064602?s=200&v=4"
I’ll work on a patch to fix that.
- Having roles on galaxy with a namespace that match some other github user’s name is always going to be confusing to end users. What would be helpful is if all the elan.* roles were renamed to elan-ev to better match the real github source. Is that something you’ve considered?