[MAGNOLIA-7779] Ensure server configuration is removed upon removing modules Created: 23/Apr/20  Updated: 15/Mar/21  Resolved: 15/Mar/21

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

Type: Improvement Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from MAGNOLIA-7777 Device detection causes migration diff Closed
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)

 Description   

As seen in MAGNOLIA-7777, some broken server configuration stays in place upon removal of module.
These problems can be handled by another module (e.g. remove old admincentral module config by new admincentral module).
Some modules are removed without replacement though. Those used to be handled by core module version handler which became really big.

Several proposals were raised that would address this: 

  • have some uninstaller module  
  • a dedicated tool to handle it..?
  • ?

 



 Comments   
Comment by Maxime Michel [ 15/Mar/21 ]

Not critical enough

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