Environment variable support for config files.

[apremalal]

In configuration files we might need to add place holders to ${server_home} kind of variables. Following is a sample yaml file.

serverConfigs:
 prefix : 'CORE_'
 isMaster : true
 portOffset : 0
 httpPort : 8080
 httpsPort : 8085
 adminPort : 9463
 caddyPort : 8082
 readTimeOut : 20
 writeTimeOut : 20
 certificateFile : '{{.ServerHome}}/resources/security/server.pem'
 keyFile : '{{.ServerHome}}/resources/security/server.key'
 JWTPrivateKeyFile : '{{.ServerHome}}/resources/security/private.key'
 JWTPublicKeyFile : '{{.ServerHome}}/resources/security/public.key'

I'm trying to build this as below.

1. read the original configuration and use template/text support to create a new configuration file after adding the variable values.
2. Pass the newly constructed file to viper

Can viper does this kind of variable templating out of the box?. if not isn't it worth adding that support?

[chen56]

why not?

[optimistic9527]

need support