[MAGNOLIA-1842] Default bootstrap behaviour should be safer Created: 15/Nov/07  Updated: 23/Jan/13  Resolved: 15/Nov/07

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

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1806 Refactoring / cleanup of the bootstra... 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   

1) When bootstrapping a node that has the same uuid as an existing node, we currently replace them, which can lead to pretty hairy and difficult-to-debug situations. We will now use ImportUUIDBehavior.IMPORT_UUID_COLLISION_THROW to avoid these.

Note that we still delete existing node with the same path before bootstrapping.

2) Importing in a non-existent repository should not be allowed anymore. (With the ModuleVersionHandler, one can be much more flexible and deterministic in how a module is installed and bootstrapped)


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