Add confirmed admin override for provisioning player checks
This commit is contained in:
@@ -62,6 +62,17 @@ campaign, beta, maintenance, or provisioning work. Duplicate pending requests fo
|
||||
the same action return the existing operation; a different action returns a
|
||||
conflict. Requests and events survive application restarts.
|
||||
|
||||
For a failed container stuck waiting for player status, an administrator can open
|
||||
its queued or waiting **Restart**, **Stop**, **Rebuild**, or **Destroy** operation
|
||||
and choose **Admin override…**. The confirmation modal explains the interruption
|
||||
and deletion risks. Confirming bypasses player-count and empty-server checks in
|
||||
both the controller and host agent for that operation only. The approval persists
|
||||
across restarts and records the administrator and time in the operation history.
|
||||
The host agent must support overrides (version 1.4.15 or newer); older agents show
|
||||
an update requirement. Submitted commands, host migrations, and completed operations
|
||||
cannot be overridden. Capacity, conflicting work, instance identity, file validation,
|
||||
and post-action health checks still apply.
|
||||
|
||||
Campaigns, beta runs, and maintenance submit durable restart requests to
|
||||
Provisioning and observe the resulting operation by ID. Their pages link to that
|
||||
operation, and its history links back to the requesting work. Provisioning owns
|
||||
|
||||
Reference in New Issue
Block a user