29 lines
1.8 KiB
Markdown
29 lines
1.8 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Guided creation authorizes automatic initial deployment
|
|
The Platform SHALL queue one fenced `process.install` job when the dedicated Run for a target-bound draft with a `guided-install` definition successfully registers.
|
|
|
|
#### Scenario: Dedicated Run registers for a guided draft
|
|
- **WHEN** the Run presents the valid server-scoped component identity for a guided draft
|
|
- **THEN** the Platform persists the session and queues the guided install using the stored deployment revision
|
|
- **AND** the server transitions to `installing` without another browser action
|
|
|
|
#### Scenario: The dedicated Run reconnects
|
|
- **WHEN** the Run registers again after the automatic installation has been queued
|
|
- **THEN** the Platform does not create another installation job for the same deployment revision
|
|
|
|
### Requirement: Automatic registration dispatch is non-destructive outside guided installs
|
|
The Platform SHALL NOT automatically reinstall existing-server or custom-command deployments solely because their Run registers.
|
|
|
|
#### Scenario: Existing server Run registers
|
|
- **WHEN** a target-bound draft uses `existing-server` and its dedicated Run registers
|
|
- **THEN** the Platform records the Run session without creating an installation job
|
|
|
|
### Requirement: Normal server management does not require a manual deployment click
|
|
The management console SHALL present guided deployment as automatically pending after dedicated Run registration rather than as a Deploy or Retry deploy button.
|
|
|
|
#### Scenario: Guided draft awaits Run registration
|
|
- **WHEN** an operator opens a newly created guided draft before its dedicated Run has registered
|
|
- **THEN** the console directs the operator to generate and start the dedicated Run
|
|
- **AND** it does not offer a separate Deploy or Retry deploy action
|