Load sensitive config values from "secrets"

[seoester]

Some fields of the configuration contain sensitive values:

• notif: mail: password
• regopts: <name>: password
• ? notif: mail: username
• ? regopts: <name>: username

Loading these values from a "secrets" mechanisms would be advantageous when deploying diun through an orchestration platform such as Kubernetes or Docker Swarm.
This could be achieved by reading the value from a file or an env var. Reading from an env var is a more universal pattern (12 factor app) whereas reading from a file would support the "secrets" mechanisms of both Kubernetes and Docker Swarm (and is arguably more secure).

The simplest solution I can think of is introducing additional configuration fields, e.g. notif: mail: password_file. password_file contains the path to a file from which the password is read, while perhaps truncating trailing whitespace. password would take precedence over password_file.

I could also see some benefit from providing username as a secret, as it is part of the credentials. notif: mail: credentials_file could be an alternative, where the file specified is a yaml document containing the username and password fields.

Thanks for considering this and keep up this great project :)

[crazy-max]

Hi @seoester, I like the idea!
And thanks for your support!

[crazy-max]

@Leopere Done through release 2.0.0.