Project

General

Profile

Actions

Feature #10669

closed

Forbid actions with irrelevant types of Klever deployments

Added by Evgeny Novikov about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
High
Category:
Deployment
Target version:
Start date:
01/18/2021
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

Users can easily forbid types ("development", "production", etc.) of Klever deployments they installed. After all this can cause very unpleasant consequences, e.g. whey somebody will try to update a production instance as a development one. I suggest to forbid corresponding actions.

In principle, deployment scripts can require types of Klever deployments just once during initial installation. All subsequent actions can determine these types automatically on the basis of some data stored during it.

Actions

Also available in: Atom PDF