-
Notifications
You must be signed in to change notification settings - Fork 645
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
S3: Consider not deprecating path-style access #2364
Comments
You are right, for compatible storage solutions Alpakka should continue to allow path-style access in one way or the other. Would it be possible to use the alpakka/s3/src/main/resources/reference.conf Lines 87 to 91 in 01bb7e4
|
@ennru I tried that, but maybe I configured it wrong. Do you have any input on how to make it work with MinIO using the I tried |
Alpakka uses Minio with virtual-host style access. The trick is to configure a forward-proxy and a dynamic alpakka/s3/src/test/scala/akka/stream/alpakka/s3/scaladsl/S3IntegrationSpec.scala Lines 638 to 657 in 63b22cb
|
This might not be an option for all users though and seems like an overly complicated way to stop Alpakka from spamming log warnings of path style access being deprecated. |
@KGausel Good news, @laszlovandenhoek just convinced me that we can should [re-think the path-style access settings](#2193 (comment) |
With #2392 the deprecation shows only if you don't use an |
While AWS is deprecating path-style access, many other providers of S3-like services are not. Path-style access is usually the easiest way to setup MinIO as it does not require fudging around with the DNS.
So while path-style access for AWS should be deprecated, path-style access for custom endpoints are still relevant.
For the same reason, it would be nice to have a way to disable the warning here:
alpakka/s3/src/main/scala/akka/stream/alpakka/s3/impl/HttpRequests.scala
Line 179 in 4c01bb1
I would be willing to put some work into this. The simplest way of achieving this would probably be something like un-deprecating the
withPathStyleAccess
function and remove the warning for custom endpoints.The text was updated successfully, but these errors were encountered: