Request opinions on alternate erlang config formats

[Mark Geib]

Thanks for all the opinions, much appreciated.

Since there are others in my groups that prefer the cuttlefish config
format, it sounds like maybe one approach would be to invoke cuttlefish
in a relx pre-start hook script. This would provide a way to avoid
replacing the relx generated script, but leverage the maturity of cuttlefish.

I am I missing anything with this idea.??

Mark.

> On Apr 5, 2020, at 11:54 AM, Tristan Sloughter <t@REDACTED> wrote:
> 
> I've always been meaning to try a method of shipping a little binary with the release that takes in config in some other format and outputs sys.config -- just using the relx start script hooks to run it before startup.
> 
> Not sure how small you can get a Rust compiled program to these days but if it was doable to strip it down to <1 MB I'd see that as a viable option -- could read in toml, yaml, json, etc and write out an Erlang term file (pretty sure there is a crate for that already) sys.config.
> 
> Other ideas have been extending Cue (https://cuelang.org/) or Dhall (https://dhall-lang.org/) or Starlark (https://github.com/google/starlark-go) to output Erlang term files.
> 
> But with my work none of this has materialized because its unneeded and I'm satisfied with OS environment variable replacement in sys.config.src with the environment variables populated by K8s -- so I haven't tried to create anything more complicated like above.
> 
> Tristan
>