Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-1945] Bootstrap tasks should support backup Created: 10/Dec/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Sub-task Priority: Major
Reporter: Vivian Steller Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1806 Refactoring / cleanup of the bootstra... Closed
depends upon MAGNOLIA-1939 update: Backup task Closed
Template:
Date of First Response:

 Description   

It is a very common use case that when bootstrapping content during update one would like to backup an already existing node. It would be nice if one could just pass a backupBeforeBootstrap boolean flag that indicates if the existing nodes shall be kept in a backup location.



 Comments   
Comment by Vivian Steller [ 10/Dec/07 ]

We might want to use the BackupTask to perform the backup: see MAGNOLIA-1939.

Comment by Vivian Steller [ 10/Dec/07 ]

we first should refactor the whole bootstrap mechanism (see MAGNOLIA-1806) because we definitely should always use the same method to determine the target node that the bootstrap mechanism is going to overwrite.
Currently there is no such public method which is a blocker for this task.

Comment by Vivian Steller [ 11/Dec/07 ]

resolving this we also can fix the TODO in WorkflowModuleVersionHandler (r13511, line 90).

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:31:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.