Dear experts, In the old version of galaxy I was owner of the namespace “laniakea” for our project roles. Currently, there are two namespaces “Laniakea-elixir-it”, which is derived from our GitHub organization and “laniakea” the old one. None of them belong to me, also roles versions are not there…

I figured out what is going on with the laniakea/Laniakea-elixir-it. The issue is being tracked here Loading... and the pull request here github_user should override namespace.name for legacy roles. by jctanner · Pull Request #1923 · ansible/galaxy_ng · GitHub

Namespace issue with new galaxy.ansible.com

Get Help

bittner (Peter Bittner) October 3, 2023, 10:18am 2

This is likely the same issue as the one I reported. See Data migration to the new galaxy.ansible.com

1 Like

Topic		Replies	Views
[need-help] Lost access to galaxy-ng namespace (for ansible roles) Get Help galaxy-ng	1	24	November 8, 2024
Roles namespace has changed with the new Galaxy website Get Help galaxy-ng , namespace	9	583	January 8, 2024
Please fix my galaxy namespace Get Help galaxy-ng	4	211	June 27, 2024
Orphan namespaces Get Help galaxy-ng , namespace , bug	11	350	October 6, 2023
Having trouble choosing which namespace to upload my ansible roles to Get Help galaxy-ng	3	242	November 2, 2023

Namespace issue with new galaxy.ansible.com

Related topics