separate server run bindings from deployment targets
This commit is contained in:
+19
@@ -0,0 +1,19 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Server creation is a draft-to-deployment workflow
|
||||
The management console SHALL create a server definition as a draft, even when a deployment target is selected. It MUST NOT dispatch installation until the dedicated Run has registered and the operator explicitly deploys.
|
||||
|
||||
#### Scenario: Create with a deployment target
|
||||
- **WHEN** an operator selects a compatible deployment target and confirms server creation
|
||||
- **THEN** the console reports a saved draft and guides the operator to generate and register the dedicated Run
|
||||
|
||||
#### Scenario: Deploy before Run registration
|
||||
- **WHEN** an operator tries to deploy a draft before its dedicated Run is online
|
||||
- **THEN** the platform rejects the request with a safe registration-required reason and dispatches no job
|
||||
|
||||
### Requirement: The console distinguishes target from dedicated Run
|
||||
The console SHALL label the initial selection as a deployment target and SHALL explain that it is a trusted build target, not the server's dedicated Run.
|
||||
|
||||
#### Scenario: Review server creation
|
||||
- **WHEN** an operator reviews a new server definition
|
||||
- **THEN** the review identifies the deployment target and says that a dedicated Run must be generated and registered before deployment
|
||||
Reference in New Issue
Block a user