Defer promotion snapshots to campaign activation
This commit is contained in:
@@ -207,6 +207,18 @@ Restoration and restart both wait for an empty server and restart capacity.
|
||||
The manual option holds those changes in a rollback campaign until you select
|
||||
**Resume when empty**. Promotion is always manual.
|
||||
|
||||
Confirming promotion creates a campaign without reading the existing files on
|
||||
additional servers. Each server waits for an empty lobby and restart capacity,
|
||||
then captures rollback snapshots immediately before applying its queued files
|
||||
and restarting. Campaign history records snapshot capture, and file comparisons
|
||||
become available once those snapshots are confirmed. Tested servers retain their
|
||||
original pre-beta snapshots; their composed configuration is still checked at
|
||||
promotion to determine whether another activation is needed.
|
||||
|
||||
Withdrawing changes that have not activated needs no snapshot and leaves those
|
||||
servers' files untouched. If activation was submitted but its snapshot has not
|
||||
been confirmed, reconcile the provisioning operation before rolling back.
|
||||
|
||||
Pause holds evaluation and wave advancement. Resume retains completed progress and the
|
||||
current revision's deadline, but starts new timing intervals. A fresh attempt resets
|
||||
progress and restarts deployed servers when empty. Recovery cycles repeat
|
||||
|
||||
Reference in New Issue
Block a user