[MGNLCI-13] Safety mechanism to prevent accidentally overwriting content Created: 04/Oct/16  Updated: 04/Oct/16

Status: Open
Project: Content Importer
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

When one approves/runs the import task in the pulse, the content will overwrite any existing content which shares an UUID on the content in the import file without warning.

This can be problematic with the common use case of sample content.

The system should protect the developer from accidental overwriting. To be determined is how. Maybe a simple warning / confirmation box if the UUID exists.

Scenario:
(I acknowledge that this scenario involves a lot of mistakes from a developer.)

  • A developer may import sample content such as sample pages. They may use those pages as a starting point and rename them.
  • The import could be run again, if for example a light module was removed and then re-added to an import directory. (this could be on purpose if the developer wants to see the original un-edited samples again.)
  • Developer approves the import in the pulse - they do not expect their page to be overwritten because they have renamed the page.
  • Page is overwritten. No way to get the page back, unless it was versioned.

Generated at Mon Feb 12 00:22:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.