[Feature]: Support Supabase S3 Datasource #34728
Labels
Enhancement
New feature or request
Integrations Pod
Issues related to a specific integration
S3
Issues related to the S3 plugin
Comments
ame-appsmith
added
Enhancement
github-actions
bot
added
the
Integrations Pod
|
Hi @ame-appsmith, @Nikhil-Nandagopal, I am willing to work on this. I have just created a Supabase account and a new project, and I have set up the access key and secret key. We need to provide Supabase as an S3 service in the S3 plugin, right? |
|
@AnnaHariprasad5123 yes that is correct |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Summary
Supabase has recently made its storage S3 compatible as per this article from April, 18th, 2024.
At this juncture, it is not possible to connect to Supabase's S3 storage because the error
SignatureDoesNotMatch: The request signature we calculate does not match the signature.gets returned when testing the configuration in Appsmith's S3 plugin.We need to figure out the underlying issue and provide a fix to make our S3 plugin compatible with Supabase S3's storage.
More info in this Slack thread.
Why should this be worked on?
Allowing users to connect to Supabase's S3 storage would enhance the user experience since Supabase is very popular and more users will start using this.
The text was updated successfully, but these errors were encountered: