replace all placeholders of ${SOMEVAR} in yaml configuration with ENV var

[dm82m]

first draft

[andig]

We don‘t plan to merge this. Yaml is on its way to retirement.

[dm82m]

@naltatis do you see any chance to provide this possibility also in ui config? providing a syntax for env vars so that they get replaced by corresponding env vars during runtime?

[naltatis]

@dm82m now sure how this is supposed to work. I don't see, that we add env interpolation support to each field in config ui. There are still places where we do yaml today (tariffs, ...) but we'll also migrate these to proper guided forms. I guess we need another solution.
What's the goal? Not having to repeat credentials?

[dm82m]

Within the evcc home assistant addon we can use a proxy to access home assistant api. With this we can get data from home assistant into evcc. I.e. car soc, car range etc.
To do that we need a bearer token that is available within the container as env var. it would be great to be able to use it in evcc.

As andi declined my yaml modification, which I can understand, the only way would be to add it in Ui config, but I am not skilled enough to find a proper way there.

see evcc-io/hassio-addon#142

[GrimmiMeloni]

I think this is somewhat "poweruser" space, so maybe we could do without interpolation inside the UI.
Isn't conceptually the DB just another storage (just like the YAML on the filesystem)?
The idea would be that independent of where the config comes from we could replace the vars as suggested by the PR.

[dm82m]

Fine for me, but I have technically no idea how that could be solved 😂