You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand this is a feature request and questions should be posted in the Community Forum
I searched issues and couldn’t find anything (or linked relevant results below)
Problem
When a
for example if COMPANION_AWS_BUCKET is not set, but someone tries to use Uppy S3 plugin against Companion, it will cause an error in the log file, which might trigger a false alarm in ops:
[error] c48cc354 uploader.error TypeError: s3: bucket key must be a string or a function resolving the bucket string
Solution
It was suggested that we should instead respond to the HTTP request with a status code (4xx?) with a message (and not log it as a TypeError)
Initial checklist
Problem
When a
for example if
COMPANION_AWS_BUCKET
is not set, but someone tries to use Uppy S3 plugin against Companion, it will cause an error in the log file, which might trigger a false alarm in ops:Solution
It was suggested that we should instead respond to the HTTP request with a status code (4xx?) with a message (and not log it as a TypeError)
Alternatives
leave it as is
Kind of related #4762 #4079
The text was updated successfully, but these errors were encountered: