-
Notifications
You must be signed in to change notification settings - Fork 17
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
Galaxy v3 API: update collection_url
defaults
#147
Comments
Pinging @rochacbruno @jctanner since they can probably help figuring out with what to replace it, resp. whether we can find a solution that works with both the old and the new galaxy. |
For context, these links are used in the docsite, for example see the |
On the new version of Galaxy, that URL will stop working and will redirect to the home page. The URLs must now be specific, whether it is a collection or legacy role, Collection
and Role
We don't have a catch-all like URL as we had before, the current implementation performs a lookup to figure out if the path is related to a collection or a role, but we are not bringing this functionality to the new galaxy. We may, in the future, map shorter URLs to So to answer your question, for now there is no URL that will be equivalent on old and new galaxy c/c @awcrosby |
I consider breaking every URL unacceptable. There are many places that link to collections and roles on Galaxy. IMHO, galaxy.ansible.com shouldn't switch to the new Galaxy NG codebase until redirects or some other solution is added. |
There are several options that would fix / soften several of these problems:
CC @ansible-community/community-team. |
Regarding those options...
|
@awcrosby is there already an update on 2 (like: already done, planned to be done with ETA, planned to be done without ETA, still under discussion, ...) and/or 1? Or something else? |
Option 1 should be working now (ansible/ansible-hub-ui#4090) :), |
That's not exactly the option 1 I described above, but it also works well :) For some existing collections it also shows a long list of legacy roles, but since collections are coming first I think that's ok. (Example: https://beta-galaxy.ansible.com/ui/dispatch/?pathname=%2Fcommunity%2Fdns) BTW, https://beta-galaxy.ansible.com/ui/ is still advertising AnsibleFest in May 2023 :) |
@felixfontein we are changing that image soon |
Yeah, that was a bug :) fixed in ansible/ansible-hub-ui#4144, should come to beta-galaxy soon |
I created #220 to update the |
The current default is
{"*": "https://galaxy.ansible.com/{namespace}/{name}"}
, which will likely not work for arbitrary collections for the new Ansible Community Galaxy.The text was updated successfully, but these errors were encountered: