# \[regression?\] galaxy ng namespace with "-" vs "\_"

**URL:** <https://forum.ansible.com/t/regression-galaxy-ng-namespace-with-vs/2259>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [November 9, 2023, 10:11am UTC](https://forum.ansible.com/t/regression-galaxy-ng-namespace-with-vs/2259 "2023-11-09T10:11:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![resmo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/resmo/32/470_2.png) [@resmo](https://forum.ansible.com/u/resmo)\
**Post date:** [November 9, 2023, 10:11am UTC](https://forum.ansible.com/t/regression-galaxy-ng-namespace-with-vs/2259/1 "2023-11-09T10:11:50Z")

</div>

Hi

I have a gh handle `ngine-io` but the old galaxy didn’t allow dashes in the namespace: so I got `ngine_io`.

However, for import into galaxy I used to use ngine-io like so

```auto
ansible-galaxy role import --api-key "$ANSIBLE_GALAXY_API_KEY" --role hcloud ngine-io ansible-role-hcloud 

```

But this failed in galaxy-ng with `ERROR! None (HTTP Code: 403, Message: Forbidden)`

After changing it to

```auto
ansible-galaxy role import --api-key "$ANSIBLE_GALAXY_API_KEY" --role hcloud ngine_io ansible-role-hcloud 

```

the upload was successful.

A quick namespace lookup with “\_” shows 413 namespaces. I guess those will run into the same issue when uploading.

So I would suggest to let them know by adding a proper error message in the log if the namespace does have a \_ in it.

just FYI

---

<div class="post-metadata">

**Author:** ![chynasan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chynasan/32/1022_2.png) [@chynasan](https://forum.ansible.com/u/chynasan)\
**Post date:** [November 14, 2023, 3:58pm UTC](https://forum.ansible.com/t/regression-galaxy-ng-namespace-with-vs/2259/2 "2023-11-14T15:58:14Z")

</div>

This is a bit of a complex issue due to the pulp code on top of Django, but we are actively working on and tracking this in [Jira AAH-2861](https://issues.redhat.com/browse/AAH-2861).