[MGNLDAM-462] (Potentially) long running actions should be configured to run asynchronously Created: 03/Jun/14  Updated: 04/Jun/14  Resolved: 03/Jun/14

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: Improvement Priority: Critical
Reporter: Daniel Lipp Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLDAM-441 (Potentially) long running actions sh... 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   

With MGNLUI-2783 we introduced a way to run commands asynchronously. Apply this during update was done in MGNLDAM-441 and we need to apply this also on fresh installation.

  • recursive publication
  • deletion

as both of the actions involve versioning of content and can be time consuming


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