[EXTDAM-167] (S3) Show orphan assets in tree Created: 14/Oct/20  Updated: 16/Nov/20  Resolved: 26/Oct/20

Status: Closed
Project: External DAMs
Component/s: s3
Affects Version/s: 1.0, 1.0.1
Fix Version/s: 1.0.2

Type: Bug Priority: Neutral
Reporter: Jesus Alonso Assignee: Jesus Alonso
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: 0.5h
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  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: DAM Phase 2
Sprint: Add-Ons 49
Story Points: 3

 Description   

S3 uses the key attribute to somehow identify a tree hierarchy. However, the key is arbitrary and programatically, it is possible to add into S3 assets without a parent folder.

For instance, you could create these assets:

/bucket/20201014/file1
/bucket/20201014/file2
/bucket/20201014/file3

And it is not required to create the folder object with key

/bucket/20201014

In such a case, the assets above would not be shown in the S3 tree. Notice that if you use the S3 console, this would never happen, as you always have to create the folder.

AC

  • Detect orphans assets rendering the tree
  • Generate on the fly the missing folders.

For instance, in the example above, the folderĀ /bucket/20201014 should be shown in the tree.


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