-
Notifications
You must be signed in to change notification settings - Fork 0
Web app can delete file in S3 #29
Comments
Feature/delete file in s3 refactor #29
…-a-file-#29 Testing/add unit tests for deleting a file #29
Up-to-date Acceptance Criteria Should return a warning message if the bucket or the file does not exist at the S3 end Otherwise, deletes the file and returns a message confirming the deletion Testing ❌ Problem caused when a file path is given that goes outside the bucket - eg {"bucket": "ditto-anything-i-want", "file": ".."}. Also applies when "file": "" is given
|
…directory-outside-of-root/#29
…directory-outside-of-root/#29
…-root-#29 Identical dir paths without final backslash are accepted as equal
Problem caused by attempting to delete a file outside of the root directory has been resolved. This now returns a 403 Forbidden error instead of the previous 500 error |
Story points: 2
A DELETE request to the Web API (route "deletefile") deletes a single file at the S3 end
Acceptance criteria:
GET request to: http://172.28.129.160:8888/deletefile/{bucket-name}/{relative-path-to-file} (e.g. http://172.28.129.160:8888/deletefile/test-bucket/testdir/testfile.txt)
Should return a warning message if the bucket or the file does not exist at the S3 end
Otherwise, deletes the file and returns a message confirming the deletion
The text was updated successfully, but these errors were encountered: