-
Notifications
You must be signed in to change notification settings - Fork 1.4k
system_config: support built-in config files #4893
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
Conversation
This is just a PoC. |
238d9dc
to
49f544d
Compare
b1329d3
to
aa12263
Compare
0bd54d9
to
30467dd
Compare
See fluent/fluentd#4893 Signed-off-by: Kentaro Hayashi <[email protected]>
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.
It would be necessary to add more tests.
At least, we want to confirm that some additional configs are merged correctly.
Currently @include directive supports to reuse configuration files, but no way to apply specific configuration files by default (without specifying to). In the previous versions, if you want to manage multiple configuration files, you must use @include directive explicitly. In this commit, add an option to specify the directory (e.g. /etc/fluent/conf.d) which stores additional configuration files. If there are such files under specified directory, they are loaded by default without @include directive. If you want to disable this feature, set empty string for config_include_dir "". Signed-off-by: Kentaro Hayashi <[email protected]>
Co-authored-by: Daijiro Fukuda <[email protected]> Signed-off-by: Kentaro Hayashi <[email protected]>
Rebased with master and squash feedback commits. |
Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
Before: stub all Fluent::Config.build After stub first Fluent::Config.build, do not stub additional Fluent::Config.build Signed-off-by: Kentaro Hayashi <[email protected]>
Followed feedback (Use stub.proxy) |
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.
👍🏻
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.
LGTM! Thanks!
Could you update the description of this PR?
|
Updated! |
Which issue(s) this PR fixes:
N/A
What this PR does / why we need it:
Currently
@include
directive supports to reuse configuration files, but no way toapply specific configuration files by default (without specifying to).
For example, if this feature was merged, a specific configuration could be applied in any case for fluent-package.
By putting some conf files under /etc/fluent/conf.d/*.conf.
Docs Changes:
fluent/fluentd-docs-gitbook#577
Release Note: