Skip to content
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

Closed
rarkins opened this issue Oct 3, 2023 · 4 comments · Fixed by #25239
Closed

Migrate galaxy-collection datasource from v2 to v3 #24981

rarkins opened this issue Oct 3, 2023 · 4 comments · Fixed by #25239
Labels
datasource:galaxy-collection help wanted Help is needed or welcomed on this issue priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Oct 3, 2023

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/

@rarkins rarkins added type:feature Feature (new functionality) priority-2-high Bugs impacting wide number of users or very important features status:ready datasource:galaxy-collection labels Oct 3, 2023
@rarkins rarkins added the help wanted Help is needed or welcomed on this issue label Oct 3, 2023
@rarkins
Copy link
Collaborator Author

rarkins commented Oct 3, 2023

@secustor
Copy link
Collaborator

secustor commented Oct 3, 2023

For reference there seems to be a general issue with the API currently

ansible/galaxy#3253 (comment)

@fust
Copy link

fust commented Oct 13, 2023

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
This is around the same time we were starting to see errors for Galaxy dependencies in our Renovate pipelines.
I can't find anything on the v2 API for ansible/galaxy_ng which leads me to believe that it won't be coming back.

@secustor
Copy link
Collaborator

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.

@secustor secustor changed the title Migrate galaxy-collection datasource from v2 to v3 Migrate galaxy & galaxy-collection datasource from v2 to v3 Oct 13, 2023
@secustor secustor changed the title Migrate galaxy & galaxy-collection datasource from v2 to v3 Migrate galaxy-collection datasource from v2 to v3 Oct 15, 2023
@rarkins rarkins added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others and removed priority-2-high Bugs impacting wide number of users or very important features labels Oct 15, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
datasource:galaxy-collection help wanted Help is needed or welcomed on this issue priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants