Summary
Deploying a custom connector in yaml format without using the UI, possibly through helm values.yml, terraform, or the API.
Question
Hi there,
I currently have a (rather simple) custom connector in yaml format. We run Airbyte OSS on kubernetes with helm and deploy all connectors using terraform. However, I cannot find how I can deploy / upload the custom connector without using the UI, e.g. using the helm values.yml or another way.
Is it possible to deploy the custom connector through the yaml file, terraform or the API?
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
["custom-connector", "yaml-format", "airbyte-oss", "kubernetes", "helm", "terraform", "api"]
There’s no nice clean way to configure it. I’d like to see terraform option for that as well…
Few hacks that come to my mind:
• You could check browser’s request when adding new connector
• You could write Selenium script that repeats manual way of adding new connector
• You could write script that add proper records to database, so connector will be available for use in connections
In my project, I’m adding new connectors manually.
A bruteforce workaround: just contribute that connector to Marketplace via Builder, ping us to get it merged, and then use terraform to reference the marketplace connector.
(That does not work if it’s internal one-off API, or if you want to frequently change it)
<@U069EMNRPA4> instead of workarounds, maybe some new endpoints can be added to roadmap?
I added a comment to https://github.com/airbytehq/airbyte/issues/42990