ar90n
BUG - Meta Tags on PUT Command do not work
Hi,
When creating a PUT command followed by generating a pre signed request, you are given a correct url containing meta information through the x-amz-meta headers, when you then PUT to this url, the file will be stored (in your tmp bucket) however on reviewing the meta file, the data is not contained in there.
Steps to reproduce
` /** @var CommandInterface $cmd */ $cmd = $this->s3ClientService->client->getCommand('PutObject', [ 'Bucket' => env('S3_BUCKET'), 'Key' => 'imports/' . $filename, 'Metadata' => [ 'import_id' => $import->id, ], ]);
$preSignedRequest = $this->s3ClientService->client->createPresignedRequest($cmd, '+5 minutes');`
This generates the correct presigned url, when you PUT the file to that url, check your /tmp/bucket/keylocation folder look at the meta tag file and the import id will not be there.
NOTE: Locally this does not work On a DEV environment using actual AWS, this does work.
@pl4yradam Thanks for your report. I'm so sorry for inconvenience. It seems that this issue is caused by the restriction of s3rver which is a backend of serverless-s3-local. So this feature is not supported for now.
Has the bug been raised there yet then linking here?
On Fri, 7 Feb 2020, 22:08 Masahiro Wada, [email protected] wrote:
@pl4yradam https://github.com/pl4yradam Thanks for your report. I'm so sorry for inconvenience. It seems that this issue is caused by the restriction of s3rver which is a backend of serverless-s3-local. So this feature is not supported for now.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ar90n/serverless-s3-local/issues/89?email_source=notifications&email_token=AFL4VWWQGABPGEX42WOMT6DRBXLVFA5CNFSM4KRNI3DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELEZSFA#issuecomment-583637268, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFL4VWUCCTAGXH2YASWQL63RBXLVFANCNFSM4KRNI3DA .
Hey @ar90n it looks like they got back on https://github.com/jamhall/s3rver/issues/591, is there any update for this fix?
