Skip to content

fix(s3): read objects directly by key

Винник Артем requested to merge fix/s3-object-read into master

What changed: Read known keys directly, share cancellation across retrieval and copying, and dispose responses. Add focused service tests. Why: Searching one list response could miss an existing object. The previous implementation searched only the first ListObjectsV2Async response, which contains up to 1,000 object keys. It did not request subsequent pages. In a larger bucket, an existing EML file outside the first response could therefore be incorrectly reported as missing. The object key is already known, so GetObjectAsync retrieves it directly without listing the bucket or depending on pagination. Verification: 18 service cases passed; the existing mixed CA/TO integration scenario passed in Release with MinIO.

Merge request reports

Loading