-
Notifications
You must be signed in to change notification settings - Fork 226
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
fix: gcs endpoint should be independently configured with credential #837
Conversation
Pull Request Test Coverage Report for Build 7961810108Details
💛 - Coveralls |
Would you like improve your PR to add integration test for https://github.com/fsouza/fake-gcs-server? |
6cb573d
to
904df78
Compare
Looks good, did you try
?? |
904df78
to
43c91b4
Compare
862abee
to
901f61b
Compare
Hi @Slach , thank you for some pointers.
|
i don't understand why you try to fix
|
sorry I saw you have different test for GCS with custom endpoint with properly config |
it looks weird, looks like look |
901f61b
to
f2baf64
Compare
Hi @Slach thanks again for your guidance.
yes, I reverted regardless. Don't want to pollute git history.
The issue is that Progressso I made a progress on this but to be honest I don't think fake-gcs-server supports S3 interoperability yet. See fsouza/fake-gcs-server#1330
I am not Clickhouse expert, but I am sure Clickhouse is using S3 SDK, given the If I disable
now I am in circle, if I enable this |
The failing tests seem unrelated to my changes |
|
Thanks @Slach , the integration test has passed now 😄
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will try to fix failed tests later
@Slach is there planned release soon? |
Superb, thanks a lot 👍 |
Hi, I would like to propose to decouple gcs endpoint configuration with credentials.
Use case: We're connecting to gcs via private service connect:
https://cloud.google.com/vpc/docs/private-service-connect?authuser=1&_ga=2.220919888.-993337742.1685727395#supported-apis
The access control should stay the same regardless where the bucket is accessed from.
Let me know what do you think. Appreciate any feedback!