Enable providing endpoint_url through environment variables#704
Conversation
|
WIth this code change it is possible to set environment variables to fully control connections to non-AWS S3 buckets, like local minio or S3-compatible store in other clouds.
|
|
Thakns - I suppose this is indeed common enough that it deserves its own top-level argument. This argument should be documented; ideally, we should specify which once wins in the case that an endpoint is included in both this explicit arg and also in the client_kwargs. |
|
@martindurant take a look please, I've updated docstring. Also it seems reasonable to me, to add short article to docs named something like "Connecting to non-AWS buckets", but I do not understand yet how to do it in the correct way. |
|
All the docs are in docs/source, a few RST files there. I'm not immediately sure where this would fit in, but there is not too much prose there. I am happy to wait on this PR if you have the time to add something. |
|
I added some changes to index.rst If you're ok with the changes, then I think PR is complete. |
|
Can you please investigate the failing test, and see whether it is caused by this PR (i.e., does it fail if you check out main branch). |
|
Oh wow, will do |
|
|
Yeah, I did not get to the bottom of it yet. |
|
Fixed. That was an actual bug on my side. Thanks so much for extensive tests |
|
Glad we caught it :) |
Currently, if you're using non-AWS S3 endpoint you're stuck with less ergonomic syntax, see #120 (comment) for example.
Sometimes it's feasible, but sometimes it breaks flexibility that
fsspecprovides.This simple PR makes
endpoint_urla first-class configuration option, alongside withkeyandsecret, which are already supported exactly in the same way.