feat: Deletion of resources on AWS S3 #335
Merged
Merged
Conversation
added 6 commits
March 12, 2026 14:33
DavidPavlovski
requested changes
Mar 19, 2026
DavidPavlovski
approved these changes
Mar 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed?
Why?
delete-file/{id}endpoint, we ensure a full lifecycle cleanup of resources, reducing storage overhead and maintaining data consistency.Closes #334
Type of Change
How Did You Test This?
DELETEendpoint viaSwagger UIto verify the end-to-end flow from the API layer to AWS.AWS Management Consoleto confirm the physical object was successfully removed from the S3 bucket.What I tested:
How to test it:
Review Checklist
Screenshots / Additional Context