EMC currently uses one evelyn.perps.default service instance for both TEST and PROD. Replace it with two separately configured instances while preserving the existing Perps UI.
Scope
Create evelyn.perps.test and evelyn.perps.prod using the existing service lifecycle conventions.
Define the hardcoded wallet list in NenjimHub's construction code and pass it to each service instance at construction time. Use the same list for both instances for now.
Each service instance retains its configured wallets and owns its own positions snapshot.
Connect EMC's TEST and PROD tabs to their respective service instances.
Preserve automatic polling every three seconds and the parameterless getPositionsSnapshot() operation.
Update startup configuration and dependency references to use the new instance names.
Keep the existing hardcoded sample positions and presentation. Real integrations, position management, and a more advanced configuration mechanism are outside this task.
Acceptance criteria
Two separate Perps service instances are configured and started: evelyn.perps.test and evelyn.perps.prod.
Both receive the same wallet configuration from NenjimHub; the service implementation no longer defines the wallet list itself.
EMC retrieves TEST data exclusively from the TEST instance and PROD data exclusively from the PROD instance.
EMC neither owns nor passes wallet configuration.
The existing Perps appearance, sample-data indication, expansion state, and selection are preserved across polling cycles.
Startup no longer depends on evelyn.perps.default.
EMC currently uses one `evelyn.perps.default` service instance for both TEST and PROD. Replace it with two separately configured instances while preserving the existing Perps UI.
**Scope**
- Create `evelyn.perps.test` and `evelyn.perps.prod` using the existing service lifecycle conventions.
- Define the hardcoded wallet list in NenjimHub's construction code and pass it to each service instance at construction time. Use the same list for both instances for now.
- Each service instance retains its configured wallets and owns its own positions snapshot.
- Connect EMC's TEST and PROD tabs to their respective service instances.
- Preserve automatic polling every three seconds and the parameterless `getPositionsSnapshot()` operation.
- Update startup configuration and dependency references to use the new instance names.
Keep the existing hardcoded sample positions and presentation. Real integrations, position management, and a more advanced configuration mechanism are outside this task.
**Acceptance criteria**
- Two separate Perps service instances are configured and started: `evelyn.perps.test` and `evelyn.perps.prod`.
- Both receive the same wallet configuration from NenjimHub; the service implementation no longer defines the wallet list itself.
- EMC retrieves TEST data exclusively from the TEST instance and PROD data exclusively from the PROD instance.
- EMC neither owns nor passes wallet configuration.
- The existing Perps appearance, sample-data indication, expansion state, and selection are preserved across polling cycles.
- Startup no longer depends on `evelyn.perps.default`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
EMC currently uses one
evelyn.perps.defaultservice instance for both TEST and PROD. Replace it with two separately configured instances while preserving the existing Perps UI.Scope
evelyn.perps.testandevelyn.perps.produsing the existing service lifecycle conventions.getPositionsSnapshot()operation.Keep the existing hardcoded sample positions and presentation. Real integrations, position management, and a more advanced configuration mechanism are outside this task.
Acceptance criteria
evelyn.perps.testandevelyn.perps.prod.evelyn.perps.default.