[PB-5721] fix(thumbnail): use file bucket instead of request bucket for storage #913
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 does this PR do?
Fixes thumbnail storage bucket inconsistency by ensuring thumbnails always use the file's bucket instead of the bucket from the request DTO.
Why are we doing this?
Thumbnails were being created using the
bucketIdfrom the request DTO, which could differ from the actual file's bucket. This caused issues in workspace environments where:How are we doing this?
createThumbnailto usefile.bucketinstead ofcreateThumbnailDto.bucketIdexistingThumbnail.bucketId(where it actually exists) instead of the new bucket for backward compatibilityfile.bucketAny background context you want to provide?
This fix ensures proper bucket isolation between personal and workspace files, and handles migration of thumbnails created before this fix was implemented.