[ANN] Configs.jl: Opinionated tool for managing deployment configurations

Package Announcements
3

I want to preserve immutability after all the setconf! calls are done, so an “on the fly” temporary node is unwanted. This is also how Node conf works, and the principle is that configurations should never be able to cause a side affect once set.

setconfig! is pretty flexible:

setconfig!("database.connection.port", 2000)
setconfig!("database", Dict("connection" => Dict("port" => 2000)))

You have made me think that this could also be useful:

setconfig!("database", """{
    "connection": {
        "port": 2000
    }
}""")

so that retrieving a bulk JSON payload from external source can be input directly.