You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @derElektrobesen! thanks for the contribution
there are still some changes needed for the workflows to pass, please refer to this PR for an example of similar connector changes for Conduit 0.13, and let us know if you have any questions 😄
@derElektrobesen thank you for your contribution!
can you please tell us more about your use case for this connector, and what destination connector you're using? we'd love to know more about Conduit use cases for our users.
feel free to also join our discord if you haven't already! We'd love to hear from you there, and reach out to the team :D
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
MySQL connector config parsing lost after conduit-connector-sdk library upgrading from v0.12.0 to v0.13.0
Fixes # (issue)
Quick checks: