I’m trying to import a new version of my role with this command (also tried with a Github action, same result - and also created a new token because I got a “403 - permission denied” with the first attempt):
ansible-galaxy role import --api-key <…> githubixx ansible-role-etcd
Successfully submitted import request 2052239628262167152290618988517025690
githubixx.etcd 9.1.0+3.4.7 has already been imported
File “/venv/lib64/python3.11/site-packages/pulpcore/tasking/tasks.py”, line 66, in _execute_task
result = func(*args, **kwargs)
File “/app/galaxy_ng/app/api/v1/tasks.py”, line 145, in legacy_role_import
ansible-galaxy [core 2.15.4]
config file = None
configured module search path = [‘/usr/share/ansible/plugins/modules’]
ansible python module location = /usr/lib/python3.11/site-packages/ansible
ansible collection location = /usr/share/ansible/collections
executable location = /usr/bin/ansible-galaxy
python version = 3.11.5 (main, Sep 2 2023, 14:16:33) [GCC 13.2.1 20230801] (/usr/bin/python)
jinja version = 3.1.2
libyaml = True
Before Galaxy NG this always worked. I mean “9.1.0+3.4.7” is already imported, that’s true. But how should I import otherwise? I can’t specify a tag e.g.
But besides that in general I can really just agree with The new Galaxy is completely broken . E.g. most of the versions of my roles just don’t match anymore with the tags I have in the Github repos: Galaxy NG
Then calling everything “role” like legacy is just strange (at least one feels like that using Galaxy NG). There are way more roles out there then collections and why create a collection if you’d only have one role in the collection? This is really telling all the role authors out there: “Go away! We don’t want you anymore!” At least that’s my impression right now.
The new UI looks like some retro pages from around year 2000 or so. Also why do I’ve to go to “Collections” to find my API token (needed to read the documentation to find it…)? Not very intuitive. At the end that belongs to the user settings/preferences IMHO.
Then the role names are not correct. E.g.
I renamed them a while ago to get rid of the “-” because “ansible-lint” was always complaining that this is not correct with the dash. But when I first started with that role names years ago it wasn’t an issue. Also here the version numbers are not correct.
I guess there are still way more issues out there. Today I only wanted to update my etcd role. But yeah, got lost somewhere
Sorry for the rant but I do all that in my free time and currently Galaxy NG is just consuming my spare time and there is nothing I get back. I don’t see a single plus with Galaxy NG as a role developer right now.