Request opinions on alternate erlang config formats

[Mark Geib]

I have been tasked with looking into alternatives to the 
sys.config configuration for erlang releases that are more
palpable for non-erlangers. In my group there are non-erlang
developers that suggest property based key=value configs, and
others that suggest yaml.

I have looked into cuttlefish, but have reservations regarding
how it replaces the relx management script for a release, I
use rebar3. Also, there will certainly be times where structured
config is necessary and cuttlefish’s limitations will make that
difficult.

I have also looked at yaml parsers, basically transforming the
yaml config into erlang terms mimicking the sys.conf, and then
in my application start, I set the environment for the application
from this. This sort of works in the simple cases, but when you
need to configure multiple applications, like logger, then it
gets hard to do something general purpose. And I have not even
looked into how to handle dependencies that could have yaml
configs, etc.

So, does anyone use anything other than sys.conf, i.e. the native
erlang configuration, and if so what do you suggest.??

Also, is this really a problem.?? I have no problem with sys.conf,
but I write erlang and don’t get squeamish looking at nested braces.

Thanks, and I welcome all opinions.

Mark.