-
Notifications
You must be signed in to change notification settings - Fork 194
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
Support for GCS private conda registry. #1922
Comments
I think this makes sense, we should do the changes in the gateway I think. Is it normat to use the |
I think so for google-cloud-storage :) But feel free to change if needed! |
We will have to add this to the gateway indeed! Ill try to take a look at that this week! |
Docker support is not yet completely finalized in the conda ecosystem. There is an active Conda Enhancement Proposal that covers this use case. We might want to wait until that has been finalized. |
We do have or had support for the |
I read this completely wrong, I was under the impression that you wanted to use the docker registry API. I drafted a fix in conda/rattler#845 that hopefully works for your case. |
Hello @baszalmstra This issue should be reopened because it doesnt work as expected: So now the "gcs" scheme is supported (not getting The gcs URL should be converted later in the gcs_middleware.rs to https://storage.googleapis.com to handle the auth. I have also pushed a PR to add the GCS middleware to pixi (cannot test it yet) |
Problem description
Hello,
I would like Pixi to support private conda registry hosted on GCS buckets.
I had actually pushed a PR to rattler a few months ago to have this GCS Middleware support.
I used to test with something like this but never merged it.
Because of some changes to the
rattler_repodata_gateway/gateway
crate, I now have:And I m not sure how to make it work anymore.
Could you have a look and try to support :
Thanks for your help!
The text was updated successfully, but these errors were encountered: