Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passing secrets or env vars to the config.yaml #609

Open
denysdovhan opened this issue Mar 4, 2023 · 2 comments · May be fixed by #735
Open

Passing secrets or env vars to the config.yaml #609

denysdovhan opened this issue Mar 4, 2023 · 2 comments · May be fixed by #735

Comments

@denysdovhan
Copy link

Is your feature request related to a problem? Please describe.

Hey! Thanks for this project!

Is there a way to pass secrets into config.yaml file via some sort of keyword?

Describe the solution you'd like

For example, Home Assistant and zigbee2mqtt projects provide an ability to pass secrets or env vars via keywords in a YAML files. Like this:

token: !env TOKEN_ENV_VARIABLE
# or
token: !secret token # token field from secrets.yaml file

Describe alternatives you've considered

¯_(ツ)_/¯

Additional context

I am open sourcing my smart home config and would like to use Homer for a dashboard of my smart home server. I would love to publish my config, by I also need to pass some secrets to the config (like token for Portainer or Pi Hole, etc)

@ocelot2123
Copy link

+1 to this, especially because I put my homer config on github, would be great to not have to track those API keys

@GwynHannay
Copy link

Another +1 here!

@flooxo flooxo linked a pull request Jan 12, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants