-
Notifications
You must be signed in to change notification settings - Fork 7
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
Galactory no longer support proxying to galaxy.ansible.com out of the box #119
Comments
Hi @mshonichev , welcome! Thanks for the including so much info in this report, that's very helpful. This line is especially interesting:
It means that the request from the Typically that means that the client detected no If you hit Also, because you're using the Finally, it might be helpful to add I have one theory so far: |
Yep, you're absolutely right! So, production setting to proxy for https://galaxy.ansible.com is to use AND Don't forget to clear response cache at client side, e.g.:
I see you don't plan to automatically forward Thank you so much for your support! |
Glad to hear that worked! Indeed I don't plan to explicitly support Thanks very much for your interest in the software, I'd love to hear more about how you're using it and what your experience has been. |
One other thing to clarify (for anyone reading) is that you don't have to use In this case clearing the cache (or using |
Hello, Brian!
First of all thank you for the great software package you've delivered!
I try to use Galactory in scenario 'proxy/caching the upstream Ansible Galaxy' as to lower the outgoing bandwidth for the CI.
Recently, Ansible Galaxy NG has gone out of the beta and they bumped their main site to the 'v3' API version.
If we browse directly to https://galaxy.ansible.com/api/ we would see that no 'v2' API is supported now.
Which leads me to the problem, Galactory can no longer proxy requests to the upstream Galaxy, because
ansible-galaxy
client seems to ultimately using 'v2' version when negotiating with Galactory, no matter which--api-version
option value I use.Scenario:
Galactory galactory:0.11.1 image is running with following options:
client version & test command:
Log:
However, if use galaxy.ansible.com directly, the collection is installed successfully:
Is there any workaround or quick fix for this situation?
The text was updated successfully, but these errors were encountered: