-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
promtail: change to use viper #644
Conversation
2171de9
to
d338a03
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you it's great but just like this it doesn't improve or help though it brings a lot of new dependencies.
I think if you want to take care of this we should also set default using viper, parse flag and file and merge everything together.
8751f23
to
fa560af
Compare
@Kuqd hi, i delete unrelated dependencies, now it support parse flags with default value and then read config, what do you mean about merge? looks like issue in #638? |
@Kuqd met a confused issue, viper get config but can not pack them into config sturct:
|
file issue to viper |
Signed-off-by: Xiang Dai <764524258@qq.com>
Signed-off-by: Xiang Dai <764524258@qq.com>
If use viper, since
On the other hand, all |
Closing this in favor of #980 which implements correct configuration source precedence (defaults < yaml < flag). Thanks for your contribution! |
Signed-off-by: Xiang Dai 764524258@qq.com
Which issue(s) this PR fixes:
Fixes #520