Ansible: can't update galaxy roles when multiple results exist #30166
Replies: 3 comments 4 replies
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
Do you have a suggestion for how to resolve it? e.g. if multiple results exist, then merge them all? |
Beta Was this translation helpful? Give feedback.
-
Related: #29664 |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Gitea
Please tell us more about your question or problem
In the new ansible galaxy it's possible for a user (namespace) to exist twice. Once from the old galaxy with the name forced to lower case and once from the galaxy with the name exactly as on github.
It has been made so both spellings of the namespace lead to the page.
Example:
Currently the following code is getting triggered, and causing the role not to be updated:
renovate/lib/modules/datasource/galaxy/index.ts
Lines 54 to 59 in 198de58
Instead of checking if we received more than one item. Consider items where the the namespace converted to lower case are equal as the same package, and remove them from the list, before we check if we have more than 1 item?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions