-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate galaxy-collection datasource from v2 to v3 #24981
Comments
Reproduction repo: https://github.com/renovate-reproductions/24981 |
For reference there seems to be a general issue with the API currently |
Looks like ansible/galaxy is being superseded by ansible/galaxy_ng and the latter went live on galaxy.ansible.com on september 30: https://forum.ansible.com/t/new-ansible-galaxy/1155 |
Found the migration blog https://www.ansible.com/blog/new-ansible-galaxy Seems like they moved the old galaxy instance to https://old-galaxy.ansible.com I'm preparing a patch that will let Renovate default to that host name instead. |
Describe the proposed change(s).
It appears that the v2 Ansible Galaxy API we've been using has stopped working and that we need to migrate to v3. However I've not been able to find a definitive reference for this year, so there is still some research to be done.
This URL for example includes the word "beta" in the examples: https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/community/api_v3/
The text was updated successfully, but these errors were encountered: