[EXTDAM-259] Renaming a S3 folder containing an asset break links to that asset Created: 19/Apr/21  Updated: 17/Sep/21  Resolved: 29/Apr/21

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

Type: Bug Priority: Neutral
Reporter: Jorge Franco Assignee: Jorge Franco
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to EXTDAM-267 Clone - [S3] Renaming a S3 asset brea... Closed
is related to EXTDAM-266 Store asset information in Magnolia 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:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Epic Link: Imaging and External DAM
Sprint: Cloud Service 7, Cloud Service 8
Story Points: 8

 Description   

Steps to reproduce

  1.  In a content app, with an asset field
  2.  Create a content using an asset in S3 that is in a folder
  3. Rename in assets app the folder that contains the asset
  4. Open the content with the asset

.. Logs, screenshots, gifs...

Expected results

When I open the content, I can see the asset without errors

Actual results

Like the asset has another key, there is an error (software.amazon.awssdk.services.s3.model.NoSuchKeyException) and the asset is not available in the content

Workaround

Development notes

Maybe the problem can also happen when you rename the asset the same way that renaming the folder.



 Comments   
Comment by Jorge Franco [ 27/Apr/21 ]

We need to have some data of the assets stored in Magnolia. We need an id for each asset to create proper links. S3 is not the place to store that data and we have to think to use JCR or another alternative. So, at the moment in this task I'm going to hide buttons to rename folder and rename asset. Then at least users can't break links renaming S3 objects with the application.

 

Later I'll create a ticket to handle with the problem (EXTDAM-266). Also I'm checking in dx-core if links also are broken renaming s3 assets and will create ticket if needed.

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