[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: |
|
||||||||||||
| 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 |
| 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 ( |