Kothapalli Venkata Avinash
11/27/2025, 1:45 PMkapa.ai
11/27/2025, 1:45 PMbash docker build . -t my-custom-connectors/destination-databricks:0.1.0 Replace my-custom-connectors/destination-databricks:0.1.0 with your preferred image name and tag. ### 2. Tag the Image for Your Private Registry Tag the image according to your private Docker registry's requirements. For example, if using AWS ECR, GCP Artifact Registry, or another provider, the tag will look like: bash docker tag my-custom-connectors/destination-databricks:0.1.0 <your-registry-url>/destination-databricks:0.1.0 Check your registry provider's documentation for the correct format. ### 3. Push the Image to Your Private Docker Registry Push the tagged image to your private registry: bash docker push <your-registry-url>/destination-databricks:0.1.0 Make sure you are authenticated to your registry before pushing. This should be done from your local or CI environment where the connector source code is available [Uploading Docker-based custom connectors](https://docs.airbyte.com/platform/operator-guides/using-custom-connectors#3-push-your-connector-image-to-your-private-docker-registry). ### 4. Configure Airbyte to Use the Private Registry Ensure your Airbyte instance is configured to pull images from your private registry. If you are using Kubernetes, you may need to create a Kubernetes secret for registry authentication and reference it in your Airbyte deployment's `values.yaml`: yaml global: image: registry: <your-registry-url> imagePullSecrets: - name: regcred [Configure a custom image registry](https://docs.airbyte.com/platform/enterprise-setup/implementation-guide#configure-a-custom-image-registry) ### 5. Add the Custom Connector in Airbyte - Go to Workspace settings > Destinations. - Click New connector > Add a new Docker connector. - Enter a display name, the full Docker image name (e.g., <your-registry-url>/destination-databricks), and the image tag (e.g., 0.1.0). - (Optional) Add a documentation URL. - Click Add to save the connector. You can now use it in your Airbyte connections. [Uploading Docker-based custom connectors](https://docs.airbyte.com/platform/operator-guides/using-custom-connectors#4-use-your-custom-docker-connector-in-airbyte) --- If you need more details on authenticating to your private registry or configuring Airbyte for private images, refer to the linked documentation above.Kothapalli Venkata Avinash
11/27/2025, 1:46 PMkapa.ai
11/27/2025, 1:47 PMkapa.ai
11/27/2025, 1:47 PMbuild.gradle file to manage its dependencies and build process. This is standard for Java connectors in Airbyte. The build.gradle file is located inside the connector's directory and is used by Gradle to compile the Java code, run tests, and build the Docker image for the connector. To build the connector, you should run the following command from the root of the Airbyte project: bash ./gradlew :airbyte-integrations:connectors:destination-databricks:build This command will: - Compile the Java code for the connector. - Run any unit tests. - Build a Docker image for the connector. If you need to add or update dependencies for the connector, you should edit the build.gradle file inside the destination-databricks directory. After making changes, re-run the build command above to apply them. This process is described in the Airbyte documentation for building Java destination connectors, which applies to Destination-Databricks as well [Step 2: Build the newly generated destination](https://docs.airbyte.com/platform/1.8/connector-development/tutorials/building-a-java-destination#step-2-build-the-newly-generated-destination).Kothapalli Venkata Avinash
11/27/2025, 1:49 PMkapa.ai
11/27/2025, 1:49 PMkapa.ai
11/27/2025, 1:49 PMbash ./gradlew :airbyte-integrations:connectors:destination-databricks:build This command will compile the Java code and build a Docker image for the connector. You can manage dependencies in the build.gradle file inside the connector's directory. Each time you make changes, re-run the build command above to update the image [Step 2: Build the newly generated destination](https://docs.airbyte.com/platform/1.8/connector-development/tutorials/building-a-java-destination#step-2-build-the-newly-generated-destination). --- ### 2. Tag the Docker Image for Your Private Registry After building, tag the image for your private registry. The image will be named something like airbyte/destination-databricks:dev by default. Tag it for your registry (replace <your-registry-url> and <tag> as needed): bash docker tag airbyte/destination-databricks:dev <your-registry-url>/destination-databricks:<tag> --- ### 3. Push the Image to Your Private Docker Registry Authenticate to your private registry if required, then push the image: bash docker push <your-registry-url>/destination-databricks:<tag> You should run these commands from your local or CI environment where the connector source code is available [Uploading Docker-based custom connectors](https://docs.airbyte.com/platform/1.8/operator-guides/using-custom-connectors#3-push-your-connector-image-to-your-private-docker-registry). --- Note: - The structure of the remote tag depends on your cloud provider's container registry service. - Make sure your Airbyte instance is configured to pull images from your private registry if you plan to use this connector in production. --- If you need to configure Airbyte to use a private registry (for example, in Kubernetes), see the [custom image registry guide](https://docs.airbyte.com/platform/enterprise-setup/implementation-guide#configure-a-custom-image-registry).Kothapalli Venkata Avinash
11/27/2025, 1:50 PMkapa.ai
11/27/2025, 1:50 PMkapa.ai
11/27/2025, 1:50 PM0.1. When tagging your Docker image, simply specify the desired version in the tag. For example: bash docker tag airbyte/destination-databricks:dev <your-registry-url>/destination-databricks:0.1 docker push <your-registry-url>/destination-databricks:0.1 This approach is explicitly supported in the Airbyte documentation, which shows examples of tagging connector images with custom tags before pushing them to your private Docker registry. The tag can be any string, including a version number like 0.1 [Uploading Docker-based custom connectors](https://docs.airbyte.com/platform/1.8/operator-guides/using-custom-connectors#3-push-your-connector-image-to-your-private-docker-registry).Kothapalli Venkata Avinash
11/27/2025, 1:51 PMkapa.ai
11/27/2025, 1:51 PMkapa.ai
11/27/2025, 1:51 PMbash docker build . -t my-custom-connectors/destination-databricks:0.1 - Replace my-custom-connectors/destination-databricks:0.1 with your preferred image name and version tag. Alternatively, if you are using the default Airbyte build process for Java connectors, the image may be built as airbyte/destination-databricks:dev or similar. You can then tag it for your private registry. --- ### 2. Tag the Image for Your Private Registry Tag the image according to your private Docker registry's requirements. For example: bash docker tag my-custom-connectors/destination-databricks:0.1 <your-registry-url>/destination-databricks:0.1 - Replace <your-registry-url> with your actual registry address. --- ### 3. Push the Image to Your Private Docker Registry Push the tagged image to your private registry: bash docker push <your-registry-url>/destination-databricks:0.1 - Make sure you are authenticated to your registry before pushing. > You should run all the above commands from your local/CI environment, where your connector source code is available. > The structure of the remote tag depends on your cloud provider's container registry service. Please check their online documentation if needed [Uploading Docker-based custom connectors](https://docs.airbyte.com/platform/1.8/operator-guides/using-custom-connectors#3-push-your-connector-image-to-your-private-docker-registry). --- Summary of Steps: 1. Build and tag your connector image locally. 2. Tag the image for your private registry with the desired version (e.g., 0.1). 3. Push the image to your private Docker registry. If you need to configure Airbyte to use your private registry, refer to the relevant Airbyte documentation for your deployment type.Kothapalli Venkata Avinash
11/27/2025, 1:52 PMkapa.ai
11/27/2025, 1:52 PMkapa.ai
11/27/2025, 1:52 PMbash ./gradlew :airbyte-integrations:connectors:destination-<name>:build Replace <name> with your connector's name (e.g., databricks). This command compiles the Java code, runs unit tests, and builds a Docker image for the connector. You can manage dependencies in the build.gradle file inside your connector's directory. Each time you make changes, re-run the build command above to update the image [Step 2: Build the newly generated destination](https://docs.airbyte.com/platform/1.8/connector-development/tutorials/building-a-java-destination#step-2-build-the-newly-generated-destination). --- ### 2. Tag the Docker Image for Your Private Registry After building, the image will be named something like airbyte/destination-<name>:dev. Tag it for your private registry and desired version (e.g., 0.1): bash docker tag airbyte/destination-<name>:dev <your-registry-url>/destination-<name>:0.1 --- ### 3. Push the Image to Your Private Docker Registry Authenticate to your private registry if required, then push the image: bash docker push <your-registry-url>/destination-<name>:0.1 You should run these commands from your local or CI environment where the connector source code is available [Uploading Docker-based custom connectors](https://docs.airbyte.com/platform/1.8/operator-guides/using-custom-connectors#3-push-your-connector-image-to-your-private-docker-registry). --- Note: - The structure of the remote tag depends on your cloud provider's container registry service. - Make sure your Airbyte instance is configured to pull images from your private registry if you plan to use this connector in production. --- If you need to configure Airbyte to use a private registry, refer to the relevant Airbyte documentation for your deployment type.