-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Make default path.X available in config file #2042
Conversation
@@ -209,7 +209,7 @@ filebeat.prospectors: | |||
|
|||
# Name of the registry file. If a relative path is used, it is considered relative to the | |||
# data path. | |||
#filebeat.registry_file: registry | |||
#filebeat.registry_file: ${path.data}/registry |
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.
Writing filebeat.registry_file: ${path.data}/registry
will be equivalent with writing filebeat.registry_file: registry
, right?
I like the version with ${path.data}
as it's more explicit about where the file is searched. But we'll need to explain in the docs that these variables are automatically set somehow.
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.
yes, it's equivalent.
Code LGTM. There's a unit test failure at the moment. Unfortunately I think we don't have system tests for these, so I guess we'll need to do some manual tests to check that:
|
uh, we're missing |
@urso yeah, we don't have |
@@ -238,6 +241,8 @@ func (b *Beat) configure() error { | |||
return fmt.Errorf("error loading config file: %v", err) | |||
} | |||
|
|||
// init paths config: |
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.
Does that comment belong on line 251?
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.
line can be removed. comment left over from original failed (more complicated) approach.
Just for consistency. But as there is currently no usage for it, let's keep it out. |
Looks good on some brief manual testing. @urso happy to merge it, do you want to cleanup history or should I just squash it? |
No description provided.