BackendSelection
Which backend a node runs on (wow.backend).
Functions
Link copied to clipboard
fun memoryOptIn(activeProfiles: Collection<String>, devProfiles: Set<String>, bindHost: String?): String?
Why a node may fall back to memory when wow.backend is auto and no durable backend is available, or null when it may not: an active profile of devProfiles (wow.dev-profiles), or an internal port bound to bindHost, a loopback address, alone, the development exemption the host's safeguards share.
Link copied to clipboard
fun select(configured: String, providers: Map<String, StoreProvider>, resources: StoreResources, memoryOptIn: String? = null): String
The store type configured, auto resolved by what is available: the one durable provider of providers that resources are enough for (StoreProvider.available: PostgreSQL with a DataSource bean, MongoDB with a MongoClient bean). Several available is ambiguous, and a type configured but unavailable fails.