-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
--config flag doesn't work #110
Comments
The intended way is to actually load this from env vars as those are usually not compromised if the filesystem is compromised, and are easier to use in PaaS (Kubernetes, Heroku, ECS) as well as in Docker. It is confusing though that |
I'm aware of that, |
Do you intend on using |
No, I was just getting it started for some testing on my local machine. Removal would be fine with me. |
Oathkeeper ignores the
--config
parameter:It seems this is because
viper.SetConfigName
unsetsconfigFile
:oathkeeper/cmd/root.go
Lines 74 to 78 in 3c0c862
The text was updated successfully, but these errors were encountered: