97: Configure separate TEST and PROD instances of EvelynPerpsService
This commit is contained in:
@@ -22,8 +22,16 @@ The service SHALL own the existing eight sample positions grouped under Sample w
|
||||
- **AND** wallet B contains Jupiter ETH Long 1875.25 and SOL Short 950.00, Phoenix BTC Long 21000.00 and SOL Short 640.50
|
||||
|
||||
### Requirement: Hub owns Perps startup
|
||||
The service SHALL run as a separate Hub-managed process registered as `evelyn.perps.default`. The service API SHALL expose no lifecycle operations. Snapshot reads before process startup SHALL fail clearly.
|
||||
The service SHALL run as two separate Hub-managed processes registered as `evelyn.perps.test` and `evelyn.perps.prod`. The service API SHALL expose no lifecycle operations. Snapshot reads before process startup SHALL fail clearly.
|
||||
|
||||
#### Scenario: Service starts
|
||||
- **WHEN** the Hub starts the registered Perps process
|
||||
- **WHEN** the Hub starts either registered Perps process
|
||||
- **THEN** its service view makes the complete sample snapshot available without starting a polling or integration worker
|
||||
|
||||
### Requirement: Wallet configuration belongs to service construction
|
||||
The Hub SHALL supply the same hardcoded wallet configuration to TEST and PROD at construction. Each service SHALL retain an immutable copy and own a separate snapshot. EMC SHALL neither own nor pass wallet configuration; snapshot reads SHALL remain parameterless.
|
||||
|
||||
#### Scenario: Separate configured instances
|
||||
- **WHEN** the Hub constructs and starts both instances using the shared sample wallet configuration
|
||||
- **THEN** each snapshot contains the configured wallet identities and existing sample positions
|
||||
- **AND** the two instances own separate snapshots without defining the wallet list internally
|
||||
|
||||
Reference in New Issue
Block a user