fix(backend): use config.DB_PROVIDER instead of process.env.DB_PROVIDER in datastore.ts
- Reads validated DB_PROVIDER from Zod config instead of raw env - Removes stale isTest fallback logic (now handled by config defaults)
This commit is contained in:
parent
ea508b1fdc
commit
6acc97bf8a
@ -16,6 +16,7 @@ import {
|
||||
CosmosDatastoreProvider,
|
||||
MemoryDatastoreProvider,
|
||||
} from '@bytelyst/datastore';
|
||||
import { config } from './config.js';
|
||||
|
||||
let _provider: DatastoreProvider | null = null;
|
||||
|
||||
@ -26,10 +27,7 @@ let _provider: DatastoreProvider | null = null;
|
||||
export function initDatastore(): DatastoreProvider {
|
||||
if (_provider) return _provider;
|
||||
|
||||
const isTest = process.env.NODE_ENV === 'test';
|
||||
const dbProvider = (process.env.DB_PROVIDER || (isTest ? 'memory' : 'cosmos')).toLowerCase();
|
||||
|
||||
if (dbProvider === 'memory') {
|
||||
if (config.DB_PROVIDER === 'memory') {
|
||||
_provider = new MemoryDatastoreProvider();
|
||||
} else {
|
||||
_provider = new CosmosDatastoreProvider();
|
||||
|
||||
Loading…
Reference in New Issue
Block a user