feat: support custom server deployment drafts
This commit is contained in:
+15
@@ -0,0 +1,15 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Plugin create schemas drive server creation input
|
||||
The system SHALL publish validated plugin create-field schemas to the management console and SHALL render supported fields during server draft creation. Required fields, defaults, select options, numeric values, port values, and boolean values MUST be validated before saving.
|
||||
|
||||
#### Scenario: Create a SCUM definition
|
||||
- **WHEN** an operator chooses the SCUM plugin
|
||||
- **THEN** the console renders the declared server name, game port, query port, and maximum player fields with their declared defaults
|
||||
|
||||
### Requirement: Game configuration is distinct from runtime transport binding
|
||||
The system SHALL persist plugin create inputs as deployment configuration and MUST NOT store game ports, player limits, paths, or startup commands in runtime binding records.
|
||||
|
||||
#### Scenario: Save Minecraft port settings
|
||||
- **WHEN** an operator saves Minecraft game and RCON ports in a draft
|
||||
- **THEN** the values are retained as plugin create configuration and runtime binding remains reserved for declared transports
|
||||
Reference in New Issue
Block a user