Closed natefoo closed 7 years ago
The roles appear now, it was a permissions problem with @galaxybot's teams. However, the role still imports as galaxyproject.proftpd. It looks like Galaxy is importing roles using the GitHub repo owner name rather than the Galaxy owner name.
FWIW I am perfectly happy renaming our roles to galaxyproject
, but (back when he was still at Ansible) Michael DeHaan had asked us to change from galaxy
to galaxyprojectdotorg
due to the unfortunate project name collision.
That's the expected behavior. We changed it, maybe 2 years ago now to import under the GitHub namespace.
Ok, thanks. I guess I'll reimport our old roles, then? Or can their names be fixed somehow?
I think the right thing to do is to move them to the GitHub namespace. Otherwise, each time your team creates a role, it will be an issue.
Closing.
This issue was moved to ansible/galaxy#71
We have a project account for our roles at https://galaxy.ansible.com/galaxyprojectdotorg/ which is linked to the @galaxybot GitHub account. As I'm a member of the galaxyproject GitHub org and have granted access to that org for my individual Galaxy account, I can also see and trigger imports for galaxyprojectdotorg roles under my individual account.
We have created a new role, galaxyproject/ansible-proftpd. This role now appears under my individual Galaxy account. However, when importing under my individual account, Galaxy created the role as
galaxyproject.proftpd
rather thangalaxyprojectdotorg.proftpd
. So I logged in under thegalaxyprojectdotorg
Galaxy account using the @galaxybot GitHub account and navigated to "My Roles." The full list ofgalaxyprojectdotorg
roles was displayed there, not including the new proftpd role. Upon clicking "Refresh your Repositories from GitHub", all of the roles disappeared except galaxyprojectdotorg.galaxy.I have verified that @galaxybot has the needed permissions on the galaxyproject org. What's gone wrong here?