Block server destruction while linked to an active beta
Protect individual, bulk, and queued removals and rebuilds until beta closure. Recheck ownership before teardown and reject beta admission during pending or unresolved destruction. Fixes #36
This commit is contained in:
@@ -14,6 +14,14 @@ server, choose **Manage server** or open its **Server actions** menu.
|
||||
| Stop | Wait until empty, stop the container, and verify that Komodo reports it stopped. Keep the instance for a later Start. |
|
||||
| Destroy | Wait until empty, remove the container and Komodo deployment, then delete server files and registration. |
|
||||
|
||||
Servers linked to a running or ready-to-promote beta cannot be destroyed or
|
||||
rebuilt. Promote or roll back the beta first, including paused or failed test
|
||||
plans. Fleet removal and exact collection launches queue nothing if any server
|
||||
selected for removal belongs to an active beta. Provisioning checks again before
|
||||
teardown; already queued removals wait while their server belongs to an active
|
||||
beta. Opening a beta also requires cancelling or finishing any pending destruction
|
||||
or rebuild on its selected servers.
|
||||
|
||||
Rebuild requires confirmation because **no instance data is preserved**. Its fresh
|
||||
files come from the latest promoted setup when creation begins, including changes
|
||||
promoted while waiting. The independently saved key in **Keys** must exist before
|
||||
|
||||
Reference in New Issue
Block a user