fix(s3): Supabase Storage access issue #334
Merged
+168
−74
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
This PR is to fix a S3 fdw access issue for Supabase Storage.
What is the current behavior?
The Supabase Storage is S3 compatible but it is using path-style URL access, but current S3 fdw only supports virtual-hosted–style URL requests. This will cause "request failed, service error" error.
What is the new behavior?
Added a new server option
path_style_urlto indicate using path-style URL or not, default is not. When using with Supabase Storage, this option needs to be set to 'true'.Additional context
This PR also upgraded some dependencies for S3 fdw. Docs are also updated.