Hi everyone. Since ansible galaxy somehow morphed into galaxy-ng, I can’t figure out how to update my ansible content there or upload new roles. It feels like ansible roles are no longer wanted or supported. Most of the time I have been using robertdebock’s gh action from https://github.com/market…

@L3D I believe I have fixed the problem. Assuming your github login is “DO1JLR” and the github org|user your roles are hosted in is “roles-ansible”, you should now be able to publish in the the “roles-ansible” legacy namespace. [jtanner@corsair ~]$ curl -s https://galaxy.ansible.com/api/v1/namespac…

Another thought I had: Are there different tokens for API V1 (used for ansible roles) and API V3 (used for collections). Because I am currently using the API token from Galaxy NG .

Yeah, I’m running into similar issues. I will let you know if I figure it out with the related solution.

I looked in the API and it looks like there are some options to managed roles. See https://galaxy.ansible.com/api/v3/swagger-ui/#/Roles But I did not test it, I just saw it and got distracted by other tasks…

I was able to successfully import. Had to generate a token and create a local ansible.cfg User Guide - Galaxy NG $ ansible-galaxy role import -vv --branch master github_user github_repo

Nice it worked for you. Sadly it is still not working form me. $ ansible-galaxy role import -vv --branch main roles-ansible ansible_role_gopass ansible-galaxy [core 2.15.4] config file = /tmp/ansible/ansible.cfg configured module search path = ['/home/l3d/.ansible/plugins/modules', '/usr/shar…

I hit a similar issue when two namespaces appeared for our roles after the migration to NG. When I try an import, I either hit a 403 or an ugly Python exception. I filed issue Roles namespace has changed with the new Galaxy website · Issue #3253 · ansible/galaxy · GitHub .

Thanks for cross-posting here. We are investigating some strangeness with namespace migration right now. This report is helpful. Investigating the import issues too @L3D , thanks for the detailed notes. Also apologies about the issues you all are experiencing.

+1 here on this issue. I am also getting the 403 Forbidden error message. Getting the error that the token is malformed in the config file but I also get the same 403 when I specify the token as a command line option. ansible-galaxy [core 2.13.3] config file = /etc/ansible/ansible.cfg python ver…

Did you have anything inside the ansible.cfg file?

This is what I used, but definitely copy it at your own discretion. Not 100% sure on the correctness. $ cat ~/.ansible.cfg [galaxy] server_list = beta [galaxy_server.beta] url = https://galaxy.ansible.com/api/ token = my_token

How to Import ansible role on galaxy.ansible.com

Get Help

geerlingguy (Jeff Geerling) October 22, 2023, 4:32am 17

FYI it seems like something is a bit broken currently — I created a new / separate topic for that issue:

2 Likes

Topic		Replies	Views
"ansible-galaxy role import" is failing with an error Get Help galaxy-ng , ansible-lint	14	2697	November 29, 2023
Unable to import roles anymore: namespace different from github organization Get Help galaxy-ng , role	18	530	February 7, 2024
Cannot import role to galaxy Get Help galaxy-ng	4	117	October 21, 2024
Unable to import roles organization namespace containing underscore Get Help galaxy-ng	11	380	December 3, 2023
[need-help] Lost access to galaxy-ng namespace (for ansible roles) Get Help galaxy-ng	1	55	November 8, 2024

How to Import ansible role on galaxy.ansible.com

Related topics