-
Notifications
You must be signed in to change notification settings - Fork 50
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
[WIP] Processor plugin #1308
[WIP] Processor plugin #1308
Conversation
SourceParams map[string]Parameter | ||
DestinationParams map[string]Parameter |
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 comes probably from the connector SDK, but I believe we need only params for processors.
// records. | ||
// | ||
//nolint:revive // This interface will be moved into the SDK | ||
type ProcessorPlugin interface { |
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.
As per the conversation we had earlier: ConduitIO/conduit-processor-sdk#1
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.
The PR above was merged.
Closing in favor of #1322 |
Description
This adds a processor plugin and a builtin registry.
We should move the plugin interface into the SDK to simplify things. Then the plugin doesn't have to import Conduit and Conduit doesn't have to translate objects when sending them to the plugin (at least if it's a builtin plugin). This makes the architecture quite a bit faster and simpler than what we currently have with connector plugins.
Related to #1285
Quick checks: