Details
-
Type:
Sub-task
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Do
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: updatemechanism
-
Labels:
Description
The whole Bootstrap mechanism should be reviewed. There are currently multiple places where bootstrap is used:
- Bootstrapper (used to bootstrap data when installing webapp)
- BootstrapTasks (they use the deprecated ModuleUtil methods)
- DataImporter
All of them here and there do the same thing but do not use a common API, e.g. to:
- resolve the target node out of the filename
- not all support tar.gz files instead of xml files
- etc.
Also the usage of the ImportUUIDBehavior is sometime inconsistent used. We should probably use ImportUUIDBehavior.IMPORT_UUID_COLLISION_THROW as a default behaviour.
In general we should introduce a main BootstrapUtil class that is commonly used by all classes mentioned above.
Attachments
Issue Links
- is depended upon by
-
MAGNOLIA-1795 Review bootstrap install tasks
-
- Closed
-
-
MAGNOLIA-1945 Bootstrap tasks should support backup
-
- Closed
-
-
MAGNOLIA-1785 Write tests for various bootstrap procedures
-
- Closed
-
- is related to
-
MAGNOLIA-2245 Review and suppress usage of deprecated code
-
- Closed
-
-
MAGNOLIA-1842 Default bootstrap behaviour should be safer
-
- Closed
-
-
MAGNOLIA-2245 Review and suppress usage of deprecated code
-
- Closed
-