-
Notifications
You must be signed in to change notification settings - Fork 23
Refactor output plugin name and packages #376
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
|
@nickytd Label kind/todo does not exist. |
|
@hyperspace-insights[bot] Command |
1 similar comment
|
@hyperspace-insights[bot] Command |
|
@hyperspace-insights[bot] You have mentioned internal references in the public. Please check. |
|
@nickytd You have mentioned internal references in the public. Please check. |
|
@hyperspace-insights[bot] Command |
1 similar comment
|
@hyperspace-insights[bot] Command |
|
@rrhubenov, @dnaeon You have pull request review open invite, please check |
rrhubenov
left a comment
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
How to categorize this PR?
/kind cleanup
/area logging
What this PR does / why we need it:
This PR refactors the Fluent Bit output plugin codebase by renaming packages and files for better consistency and clarity. The main changes include renaming the
pkg/valipluginpackage topkg/plugin, updating the command directory fromcmd/fluent-bit-vali-plugintocmd/fluent-bit-output-plugin, and standardizing interface names fromValitoOutputPlugin. This refactoring improves code organization and makes the plugin structure more generic and maintainable.Code changes:
pkg/valipluginpackage topkg/pluginand updated all referencescmd/fluent-bit-vali-plugintocmd/fluent-bit-output-pluginValitoOutputPluginthroughout the codebaseout_vali.so→output_plugin.so)tests/valiplugintotests/pluginNewValiClientDecoratorFunctype from client typesAdditional context:
This is a structural refactoring that maintains the same functionality while improving code organization. The changes make the plugin more generic by removing Vali-specific naming conventions, which aligns with the goal of creating a more flexible output plugin architecture.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: