-
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
libbeat cmds do not respect instance.Settings
#10720
Comments
simitt
added a commit
to simitt/beats
that referenced
this issue
Feb 13, 2019
Ensure settings from rootCmd are respected also when calling `export` and `setup`. fixes elastic#10720
simitt
added a commit
that referenced
this issue
Feb 14, 2019
* Remove deprecated Init(), pass instance.Settings around. Ensure settings from rootCmd are respected also when calling `export` and `setup`. fixes #10720
simitt
added a commit
to simitt/beats
that referenced
this issue
Feb 15, 2019
* Remove deprecated Init(), pass instance.Settings around. Ensure settings from rootCmd are respected also when calling `export` and `setup`. fixes elastic#10720
simitt
added a commit
that referenced
this issue
Feb 15, 2019
DStape
pushed a commit
to DStape/beats
that referenced
this issue
Aug 20, 2019
* Remove deprecated Init(), pass instance.Settings around. Ensure settings from rootCmd are respected also when calling `export` and `setup`. fixes elastic#10720
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Several commands in
libbeat/cmd
do not respectinstance.Settings
, but only use dedicated attributes from it. This can lead to bugs for e.g. runningexport template
etc.The bug was originally found in elastic/apm-server#1922.
Ensure that the
settings
are passed on to all cmds and remove deprecatedInit()
.The text was updated successfully, but these errors were encountered: