Open ajinabraham opened 4 years ago
I think this is the default response for a lot of errors
Serverless: [AWS s3 404 0.519s 0 retries] listObjectsV2({
Bucket: 'xxx'
})
S3 Remover: Faild: xxx may not be empty.
Serverless: [AWS s3 404 0.519s 0 retries] listObjectsV2({
Bucket: 'xxx'
})
S3 Remover: Faild: xxx may not be empty.
Got the following error for a bucket that does not exist. At least pass back the exception received from AWS.
I got this error when I wasn't using any credentials...
You can use -v
to see verbose errors instead of the default error, which won't indicate what's happening.
@siolfyr I reimplemented this plugin due to the lack of response from maintainer, see #22. It removes the verbose option, and always logs the caught error (not just the "may not be empty" message).
Any ideas why, I don't see any debug logs regarding why the failure happened.