Project

General

Profile

Actions

Feature #10634

open

Use transactions to update Klever addons and build bases

Added by Evgeny Novikov almost 4 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Deployment
Target version:
-
Start date:
12/22/2020
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

Let's consider an example. You have successfully installed a build base, then you suddenly re-install it but something fails in the middle, e.g. because you provided an invalid source for this build base. Note, that the broken build base can be partially installed but there is no information about it in klever-inst/klever.json. Then, when you will specify the valid build base, it will not be installed because of klever-inst/klever.json says that it is already installed.

As a workaround one can specify another valid build base that differs from the build base installed in the beginning, install it and then return back the original build base.

My suggestion is to completely remove references to updated entities from klever-inst/klever.json prior to their update. In this case even when something will fail in the middle, these entities will be re-installed during subsequent installations.

No data to display

Actions

Also available in: Atom PDF