kotlin-app-config

name	kotlin-app-config
description	HOCON-based configuration with PropertiesConfig singleton for Ktor services on NAIS. Use when adding config sections, environment layering, or typed config classes. Accepts prompts in Norwegian and English. (Konfigurasjon, miljøvariabler, HOCON, PropertiesConfig, oppsett)

Kotlin Application Configuration Skill

This skill describes the HOCON + PropertiesConfig singleton pattern for Ktor services on NAIS. Config is loaded from layered HOCON files via Ktor's ApplicationConfig API.

PropertiesConfig Singleton

PropertiesConfig is a Kotlin object that holds all typed config sections as lazy properties. Call PropertiesConfig.load(config) once at startup; never re-initialize.

object PropertiesConfig {
    lateinit var config: ApplicationConfig
        private set

    val isLocal: Boolean
        get() = applicationProperties.isLocal

    val applicationProperties by lazy {
        config.property("application").getAs<ApplicationProperties>()
    }

    val postgresConfig by lazy {
        config.property("postgres").getAs<PostgresConfig>()
    }

    // Add new config sections here as lazy properties

    fun load(applicationConfig: ApplicationConfig) {
        if (!::config.isInitialized) {
            config = applicationConfig
        }
    }
}

Usage at Startup

private fun Application.module() {
    PropertiesConfig.load(environment.config.mergeWithEnv())

    val useAuthentication = PropertiesConfig.applicationProperties.useAuthentication

    if (!PropertiesConfig.isLocal) {
        // Run migrations, start scheduled jobs, etc.
    }
}

Sub-files

• See hocon-layering.md for the layered HOCON pattern (mergeWithEnv()) and example HOCON config files.
• See config-classes.md for typed config section data classes (@Serializable) and testing configuration with MockK.

Benefits

• Single source of truth: All config in one singleton, no passing config objects around
• Lazy initialization: Config sections only parsed when first accessed
• Type safety: @Serializable data class properties with compile-time field names
• Environment layering: Local overrides without touching base config
• NAIS-native: Aligns with the HOCON layering convention used across NAV services