-
Notifications
You must be signed in to change notification settings - Fork 23
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
Viper does not properly read environment variables #31
Comments
Hi @gadgethm , thanks for reporting this! will try to take a look into this at the end of this week |
May I ask you to share an example of how do you set the environment variables? |
@skibish, sure thing! I use ansible for my deployment, here's the ansible docker-container invocation I'm using:
And here's the contents of
The log messages from the ddns container are the following:
I was also able to confirm using |
Added default value to `DDNS_TOKEN` so that Viper would be able to find the key and matching env. More details can be found in spf13/viper#761. Closes #31
Added default value to `DDNS_TOKEN` so that Viper would be able to find the key and matching env. More details can be found in spf13/viper#761. Closes skibish#31
I've been having trouble getting environment variables to work for passing the api token to ddns. I've tried both within an arm64 docker container (built using the repo's dockerfile + arm64 release binary, v4.0.3) and also with direct execution of the ddns binary on my arm64 machine. In both cases, the environment variable "DDNS_TOKEN" is not recognized, and ddns simply reports that a token is required. I also tried with different environment variables as specified in the README, but none of those seem to work either.
Perhaps this is related to this stack overflow issue? https://stackoverflow.com/questions/67608629/viper-automatic-environment-does-not-read-from-environment
The text was updated successfully, but these errors were encountered: