-
Notifications
You must be signed in to change notification settings - Fork 489
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
[Merged by Bors] - feat: support custom configs in connector SDK #2910
[Merged by Bors] - feat: support custom configs in connector SDK #2910
Conversation
Added an ability to specify the custom configuration in connector package metadata. OpenApi spec is used, so complex objects can be defined as well. The validation honors this specification. |
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. Great work!
bors r+ |
`connector` macro will support any custom configs for connectors. It is done in the following way: 1. Config file is read and parsed to `serde_yaml::Value`. 2. `ConnectorConfig` is parsed from the yaml value and used to initialize Producer/Consumer. 3. User-defined config is parsed from the yaml value and passed to the user-defined function. Validation on the deployer side is done only for `ConnectorConfig` type. Each connector will be responsible for the validation of its own configs.
Build failed: |
bors r+ |
`connector` macro will support any custom configs for connectors. It is done in the following way: 1. Config file is read and parsed to `serde_yaml::Value`. 2. `ConnectorConfig` is parsed from the yaml value and used to initialize Producer/Consumer. 3. User-defined config is parsed from the yaml value and passed to the user-defined function. Validation on the deployer side is done only for `ConnectorConfig` type. Each connector will be responsible for the validation of its own configs.
Pull request successfully merged into master. Build succeeded: |
connector
macro will support any custom configs for connectors.It is done in the following way:
serde_yaml::Value
.ConnectorConfig
is parsed from the yaml value and used to initialize Producer/Consumer.Validation on the deployer side is done only for
ConnectorConfig
type.Each connector will be responsible for the validation of its own configs.