[EXTDAM-333] S3AssetProvider should throw defined exceptions with invalid itemKey Created: 17/Jan/22  Updated: 18/Oct/22  Resolved: 21/Jan/22

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: 1.1.2

Type: Bug Priority: High
Reporter: Chuong Doan Huy Assignee: Yen Lac Tue
Resolution: Fixed Votes: 0
Labels: VN-Implementation, VN-Testing
Remaining Estimate: Not Specified
Time Spent: 2d 0.75h
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by EXTDAM-337 BynderAssetProvider should throw defi... Open
dependency
is depended upon by MGNLREST-256 AssetReferenceResolver throws an exce... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Date of First Response:
Epic Link: AuthorX Maintenance
Sprint: AuthorX 1
Story Points: 3

 Description   

When REST module use S3AssetProvider to get asset, but input invalid/broken assetKey (this is very common):

EXPECTED behavior : S3AssetProvider should throw defined exceptions

CURRENT behavior : Not throw anything, return Asset

This lead to further code using that Asset and get exceptions e.g software.amazon.awssdk.services.s3.model.NoSuchKeyException: The specified key does not exist.


Generated at Mon Feb 12 01:54:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.