e92d5bc325
Complete the wiring between simulator API and registry_bridge.go to ensure positions flow correctly through the complete data path: 1. Simulator API receives node positions via POST /api/simulator/nodes 2. Positions persisted to VirtualNodeStore 3. Periodic 30s sync reads positions from store 4. Registry bridge processes positions (spread geometry for default origin) 5. Positions written to Fleet Registry database Changes in main.go: - Create VirtualNodeStore with persistence - Create FleetRegistryBridge wrapping the store - Add periodic sync goroutine (every 30s) calling SyncToRegistry - Wire simulatorHandler with both store and bridge Changes in simulator.go: - Update SimulatorHandler to accept virtualStore and registryBridge - Load existing virtual nodes from store on startup - Persist node operations (Create, Update, Delete) to store - Add logging for position flow traceability Acceptance criteria met: ✓ Positions flow from simulator to registry_bridge.go ✓ Positions correctly formatted for registry ✓ All wiring issues resolved ✓ Data path complete and functional Resolves bf-5dpu |
||
|---|---|---|
| .. | ||
| cmd | ||
| internal | ||
| test/acceptance | ||
| tests/e2e | ||
| go.mod | ||
| go.sum | ||