Rebuild beta and campaign file activations
This commit is contained in:
@@ -150,14 +150,19 @@ and post-action health checks still apply.
|
||||
|
||||
## Campaigns, betas and maintenance
|
||||
|
||||
Campaigns, beta runs, and maintenance submit durable restart requests to
|
||||
Campaign and beta file changes submit durable rebuild 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
|
||||
the empty-server check, conflict handling, restart capacity, remote command, and
|
||||
the empty-server check, conflict handling, capacity limits, remote command, and
|
||||
health verification. The callers retain file deployment, beta evidence, and
|
||||
maintenance outcome verification. Jobs remain visible while waiting for players,
|
||||
other work, or integration configuration.
|
||||
|
||||
File rebuilds require host agent 1.9.2 or later. They capture rollback snapshots
|
||||
before replacing the instance, and install the requested files over the promoted
|
||||
setup. Queued file activations wait for the agent update when necessary.
|
||||
Maintenance jobs and beta recovery cycles without file changes still use restarts.
|
||||
|
||||
[Maintenance](maintenance.md) also submits recovery operations and links each attempt
|
||||
to its incident. A failed Maintenance restart can hand its reserved slot to a rebuild
|
||||
after five minutes; unrelated recovery slots remain held. Drift campaigns follow
|
||||
|
||||
Reference in New Issue
Block a user