[MAGNOLIA-6646] Definition Decoration not removed when entire definitions directory is removed Created: 27/Apr/16  Updated: 09/Feb/17  Resolved: 27/May/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4.7, 5.5

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive antti-demo.zip    
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
Epic Link: Decorations
Sprint: Basel 46
Story Points: 2

 Description   

This was observed with filesystem origin, and not yet tested on other origins.

If a decoration file is modified, renamed or moved: The system responds as expected - the ux reflects the change in the definitions. But when the entire definitions directory is removed, or its parent "light module" directory is removed, the system does not "de-register" the decoration.

When system is restarted, the decorations are removed as expected.

To reproduce:
Add a light module to a running instance which includes a decoration.
Observe that the UX shows the decorated definition.
Remove the light module from the instance.
Observe that the UX still shows the decorated definition.

Example attached:
It adds a tab to the mtk textImage.


Generated at Mon Feb 12 04:16:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.