DBZ-8046 Add workflow to manually deploy connector to docker hub for local testing #94
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.
This pull request resolves the incompatibility of the Kafka Connect Maven plugin with Debezium 3, which previously prevented us from manually deploying the connector for testing.
Key Changes:
New Profile (pack-local-changes): This profile uses the maven-assembly-plugin to generate a directory containing all the runtime JAR files needed for running the connector. This directory can be directly installed on a Kafka Connect base image through dockerfile.
Testing dockerfile updates: JDK 11 was uninstalled and replaced with JDK 17 due to the limitation of the confluentinc/cp-kafka-connect-base:latest image. This is necessary because our connector jar can't be executed with Java 11. Also removed the usage of confluent-hub install and directly install the connector plugin with COPY.
Long-Term Recommendation: