Two namespaces with same name on Galaxy NG

Get Help
,
1

Hello,

After Galaxy NG release there are two namespaces for our Org.

Original namespace: STEAMULO
New namespace: steamulo

On the Ansible Galaxy website, there are two namespaces : Ansible Galaxy
Ansible Galaxy

But we can manage only the seconde one (steamulo).
When we upload a new version of roles, it’s not available on the new namespace.

Can you delete the old one “STEAMULO”, or merge the two namespaces ?

2 Likes
2

Hello,

We still face the same problem.

Can you please provide any fix ?

Thank you

3

I can confirm that this issue still exist in galaxy-ng. Now i have Role namespace called MonolithProjects and also monolithprojects. The new releases of the Roles are being uploaded to monolithprojects but Galaxy UI is always pointing to MonolithProjects. Can someone please fix this so we can have only our original namespaces (in my case it is MonolithProjects Ansible Galaxy

1 Like
4

Is it possible to have a return from the ansible galaxy team on this subject please ?

it’s been almost a year and we still can’t manage our organization because of the migration … It doesn’t make you want to use Ansible Galaxy and rather rely on github

5

This is something that a user with the namespace owner role can delete, so any user in the admin list here, for steamulo.

You can use curl to delete the STEAMULO (all caps) instance like this:

curl -X DELETE -H 'Authorization: token <API token>' https://galaxy.ansible.com/api/v1/namespaces/6620/

I tested and confirmed in a staging environment that this cascade deleted STEAMULO while leaving steamulo in tact.

The API user guide documentation doesn’t outline this exact scenario, but can guide you further if you need help with generating an API token.

2 Likes