[MAGNOLIA-7097] Version command should allow versioning only when node is modified Created: 21/Jul/17  Updated: 10/Oct/23

Status: Open
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Andrew Warinner Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: versioning
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-9052 Improve performance and scalability o... Open
relation
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   

The activation command (info.magnolia.module.activation.command.ActivationCommand) has a property flag - modifiedOnly - indicating if node should only be activated if it is modified.

The VersionCommand should have a similar flag so it only creates a version if the node has been modified. This would cut down on the number of versions created and reduce the size of the version store (and the need to remove old or unneeded versions).


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