-
Notifications
You must be signed in to change notification settings - Fork 183
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
Environment variables for sensitive configuration file values #560
Comments
I don't think this is yet possible, but it is a good idea, and maybe we could take this a step further. Whenever a password is required in the service code, the service invokes a function
Using these special tokens would mean that in the above example a password must not begin with either This is also extensible; imagine |
This proposal sounds great, it would extend the possibilities to have sensitive data stored on another (secure) place than the non-sensitive configuration data. |
Hi Tobias and JP, I also believe this would make a sweet feature, kudos! Because Attaching to the suggestion by @jpmens to support multiple password backends, I would like to add HashiCorp's Vault to the list. From the perspetive of Salt, where I just happen to have an example at hand, reading secrets from Vault (in this case, a TLS private key) looks like With kind regards, [1] https://docs.python.org/3.6/library/configparser.html#interpolation-of-values |
Hello again.
Where PUSHOVER_KEY is an environment variable for the container. Which I can see when I post an env in the container. |
Dear @psyciknz. Thank you for asking. We did not work on this feature yet. |
I have a need for this feature as well so I've written a pull request (#681) that implements it. |
The configuration file contains sensitive data like passwords. Is it possible to pass values via environment variables into the configuration of mqttwarn? That would allow me to e.g. share my configuration in public, without having to place passwords into the configuration file.
The text was updated successfully, but these errors were encountered: