[MAGNOLIA-6741] Node is permanently added at /config/modules/[module name] by light module descriptor - backport to 5.4.x Created: 05/Aug/16  Updated: 01/Sep/16  Resolved: 31/Aug/16

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

Type: Bug Priority: Neutral
Reporter: Christopher Zimmermann Assignee: AntonĂ­n Juran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-6711 Node is permanently added at /config/... Closed
causality
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
Sprint: Kromeriz 59
Story Points: 2

 Description   

When a light module supplies a module descriptor, a node is added in the config workspace at /modules/[module name]. This node remains even if the the directory of the light module is removed.
This should not be the case because:

  • Where possible, a light module should be gone if the directory is removed.
  • If the module is removed and added again, the install does not occur again as one would expect. (I'm not sure if this has any impact in how the dependencies are evaluated.)

To be decided
How to handle this.
Some options:

  • The node should not be added to the config workspace. (This would rule out any kind of version handling, which is probably ok for now.)
  • At startup, or on file observation: If the module is removed, the node from the config workspace should also be automatically removed.

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