Open vahidalizad opened 1 month ago
How should we proceed here; I suggest to first make the change in Parse Server https://github.com/parse-community/parse-server/issues/9268, release, and then update this PR?
How should we proceed here; I suggest to first make the change in Parse Server parse-community/parse-server#9268, release, and then update this PR?
Yes, I agree that we should update the Parse Server first, release it, and then come back to this PR. I've also fixed the bug when running npm run test on this repo. However, I noticed that the Istanbul configuration might need some adjustments to fully support async functions. I suggest we address that after merging this PR.
Great, let's take care of https://github.com/parse-community/parse-server/pull/9271 first.
Summary
This pull request migrates the S3 client implementation from AWS SDK v2 to v3.
Changes
S3Client
from@aws-sdk/client-s3
package.getObject
,putObject
, etc.) with their v3 equivalents (GetObjectCommand
,PutObjectCommand
, etc.).Notes
getSignedUrl
function in AWS SDK v3 became asynchronous due to new authentication mechanisms. However, because of the wayparse-server
is designed, this function should not be asynchronous. To address this,deasync
was used to make the function synchronous. It might be better to changeparse-server
to support the asynchronous nature of this function in the future.References
Please review the changes and provide feedback. Thank you for your time and consideration.
Closes: #197