Setting up Databend as a destination in Airbyte with self-signed CA

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Troubleshooting permission denied error when setting up Databend as a destination in Airbyte on a self-hosted instance due to https protocol and self-signed CA injection into airbyte-webapp docker container.


Question

hello

I am having issues setting up Databend as a destination in airbyte on our self hosted instance.

We are getting a permission denied error as airbyte user, and we think it’s because of the https protocol. How can I inject our self signed CA into the airbyte-webapp docker container?

Any help would be greatly appreciated!

best,


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["databend", "destination", "airbyte", "self-signed-ca", "docker-container", "permission-denied", "https"]
2

bottom line, we want to bypass the check of https

3

Is this Airbyte Open Source (OSS) or Airbyte Self-Managed Enterprise? How do you know that this is problem with https? You haven’t posted any screenshot from UI or response from an endpoint.

4

we’re full hosted, both airbyte and databend

5

it looks like an issue within destination-databend connector https://github.com/airbytehq/airbyte/blob/bda5ae0e7676e61db932f3db5e241d8fd2b0e58c/airbyte-integrations/connectors/destination-databend/destination_databend/client.py|client.py
I’d recommend building custom version of this connector and contributing to airbyte repository