We're introducing the new MySQL Connector for Conduit, which allows extraction of data from and loading data into MySQL databases. This connector supports dual operation modes, including snapshot and Change Data Capture (CDC) for the source connector, as well as a destination connector for upserting records.
New year, new release! We're excited to announce that Conduit v0.13.0 is off the press. This one includes some features we've been eager to ship for a while now.
In this new release of Conduit 0.13, we're sunsetting the flag pipelines.exit-on-error we had previously deprecated on this other announcement. Going forward, you can use pipelines.exit-on-degraded to provide the same functionality.
We'd like to let you know that Conduit v0.12.3 is now out. It contains a fix for an issue related to batching as well as internal improvements.
Conduit v0.12.2 comes with up to 5x more throughput, new CLI command for initializing Conduit and pipelines, as well as bug fixes.
We're happy to announce a new Salesforce Destination Connector 0.5 for Conduit on v0.5.0, featuring real-time data integration with Salesforce Platform Events. This release enhances your ability to publish records directly to Salesforce, leveraging the power of Platform Events for seamless real-time communication between systems.
After the recent announcement of Conduit Operator v0.0.1, we're happy to share that Conduit Operator v0.0.2 is coming with support for a Schema Registry.
We're happy to announce that we recently released Conduit Operator v0.0.1, a Kubernetes operator that extends the Kubernetes API to enhance the management of Conduit instances on our own Conduit Platform.
In this latest release (Conduit 0.12), we introduced a new flag named pipelines.exit-on-degraded that allows Conduit to exit if a pipeline enters a degraded state, while deprecating pipelines.exit-on-error. This change provides a more accurate description of the functionality.