none seems to work for me if using previously existing token
token must be renew and only "API token" under the collections part in galaxy web UI, no more preferences section and no "API token" under roles
with updated token, ansible-galaxy role import --branch main juju4 ansible-adduser is authorized and process (failing a bit after "galaxy_importer.exceptions.LegacyRoleSchemaError: unknown field in galaxy_info: LegacyGalaxyInfo.init() got an unexpected keyword argument 'standalone'". once fixed, manual import ansible-galaxy role import --branch main juju4 ansible-adduser is working)
Trying to import role after new tag is failing with above error. Example https://github.com/juju4/ansible-adduser/actions/runs/11990259755/job/33427569791
It seems syntax has changed and existing environment variable is not supported anymore either --token or --api-key per https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html ansible.cfg per https://docs.ansible.com/ansible/latest/collections_guide/collections_installing.html#configuring-the-ansible-galaxy-client
none seems to work for me if using previously existing token token must be renew and only "API token" under the collections part in galaxy web UI, no more preferences section and no "API token" under roles with updated token,
ansible-galaxy role import --branch main juju4 ansible-adduser
is authorized and process (failing a bit after "galaxy_importer.exceptions.LegacyRoleSchemaError: unknown field in galaxy_info: LegacyGalaxyInfo.init() got an unexpected keyword argument 'standalone'". once fixed, manual importansible-galaxy role import --branch main juju4 ansible-adduser
is working)