Yes, I am having trouble choosing which namespace to upload my ansible roles to.
For example, my ansible role
https://github.com/roles-ansible/ansible_role_test.git is available in
I want to use it as ansible role
l3d.test, so I add “namespace: l3d” to the meta/main.yml, see
But the galaxy role import tool only imports it into roles-ansible.test. Not only is that a namespace I don’t want to use for it, it’s also a namespace with a “-” in the name. And stuff like that has had weird effects on ansible lately.
I miss the ability to delete or at least archive roles that are no longer updated. And I miss the ability to choose the namespace I want to use.
I miss the ability to add a custom profile picture to namespaces. Especially when I don’t have control over the github user with the name of my namespace.
Which brings me to my roadmap question. Is there any thought of taking back control of ansible roles and ansible role namespaces? Is there a bigger idea of how Galaxy should look for ansible roles in the future and I am just too impatient?
Because instead of trying to get my ansible roles to work, I could say screw all the ansible roles on galaxy-ng, I will just upload ansible collections. And putting ansible roles into ansible collections is a bit of work, but absolutely possible. I did just that with my l3d.test role using the l3d.testing collection, see:
Github: https://github.com/roles-ansible/ansible_collection_test.git Galacy collection: https://galaxy.ansible.com/ui/repo/published/l3d/testing/ Ansible role l3d.test in the l3d.testing collection: https://galaxy.ansible.com/ui/repo/published/l3d/testing/content/role/test/
It depends a bit on what happened to the Ansible roles. They are now labelled as legacy. Will they be deleted in galaxy-ng one day? Is it worth spending time and energy on them?
Thank you for reading this post. I love ansible and open source and would like to share my ansible roles and collections. And I hope that sharing ansible roles via galaxy-ng will soon be fun again.
And sorry for putting the links as a code block, the last time I put them as links the anti-spam bot was very trigger-happy.