-
Notifications
You must be signed in to change notification settings - Fork 72
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
Clean up configuration generation for fluentbit configs. #146
Clean up configuration generation for fluentbit configs. #146
Conversation
b24888f
to
1880902
Compare
84471f1
to
32de84c
Compare
37357c7
to
ee44b12
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.
This is now ready for review. @quentinmit, the last commit will have minor conflicts with your branch. It does introduce useful functionality, IMO, but we can discuss reverting it as well.
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
… replicates what we have in the ops agent config.
… fluentbit.Input interface. Unify fluentbit's filters under the fluentbit.Filter interface, and fluentbit's parsers under the fluentbit.Parser interface. Wrap fluentbit's Stackdriver into the fluentbit.Output interface. Use the fluentbit.Input, fluentbit.Filter, fluentbit.Output, and fluentbit.Parser interfaces instead of the individual structs. Template expansion whitespace control is hell, so there are no longer two blank lines at the end of the config. No other changes to the generated configs.
ee44b12
to
ec5c73f
Compare
Extracted from #141.