Would be nice to not have to store the config as unencrypted json on disk as it has some sensitive data in it. I use https://github.com/getsops/sops to avoid keeping sensitive data unencrypted.
I see 2 potential paths:
-
Easy: would you consider allowing config to be fed via stdin instead? Then I could pipe it in from an encrypted json source.
-
More invasive: I would prefer loading config from env vars then various secrets-via-envs approaches will work
Would be nice to not have to store the config as unencrypted json on disk as it has some sensitive data in it. I use https://github.com/getsops/sops to avoid keeping sensitive data unencrypted.
I see 2 potential paths:
Easy: would you consider allowing config to be fed via stdin instead? Then I could pipe it in from an encrypted json source.
More invasive: I would prefer loading config from env vars then various secrets-via-envs approaches will work