I am aware you got a lot on your hands regarding the deployment of galaxy-ng, so I am sorry to keep pushing. But as there was no activity in the GitHub issue I raised, nor a reaction to my post here, I feel obliged to raise this dedicated post.
Prior to the release of galaxy-ng we had access to the following namespace: checkmk
After galaxy-ng was deployed to galaxy.ansible.com, we lost access to the checkmk namespace.
This has also happened to the admins mentioned below, although their username has not changed.
Can you double-check the access and let me know what I can do to enable this?
P.S.: My personal namespace robin-checkmk0 has this trailing 0, which is a bug if I understand correctly. Maybe you can fix that as well? There is one without the 0 already, but I have no access to it.
P.P.S.: The GitHub user thorian93 is my private account and does not seem to be affected.
The robin-checkmk v1 roles namespace is bound to the robin_checkmk v3 namespace. The v3 namespace has the hyphen replaced by an underscore as required by the v3 specifications.
You should now be able to manage other owners for those namespaces in the UI …
@tannerjc I can confirm, that the checkmk namespace is accessible again, and collection uploads work, thanks!
One thing I forgot entirely: The tribe29 namespace also belongs to the same people as mentioned above. Our company was renamed. Can you restore access there too?
I’m not sure which username you wanted to own tribe29, but I’ve added robin-checkmk and thorian93. You should be able to remove the ones you didn’t want from the UI … tribe29 namespace access tab