Enable deployment locking so it won't be deleted
Description
In some use cases, we there are two completely independent deployments one of the deployments rely on resources created by the other deployment.
Let's say that Dep A creates a network and router
Dep B uses this router.
Currently we can uninstall dep A and B won't have routing options anymore.
We need a feature where Dep B locks Dep A so it can't be deleted without uninstalling B first.
Activity
This is coupled with
please take a look at the referenced theme. it should cover dependency via the use of components, and dependency via the use of get-capabilities. does this cover the use cases that triggered this ticket or are there more?
If I read correctly it will deal only with components with shared resources, what about two deployments that are not part of any shared blueprint or capability?
The request was to be able to lock the deployment so it can’t be deleted, it is not an implicit act, since some other deployment is using the components/capabilities, it is an action a user performs to lock and avoid loosing that deployment.
Adding as story for 5.2. basic story draft at
Assignee
Reporter
Labels
Target Version
QA Owner
Premium Only
Documentation Required
Why Blocked?
Release Notes
Priority
Epic Link
Priority
