Managing custom source connector YAML in Terraform or via API

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

User is looking for a way to manage a custom source connector YAML in Terraform or via the API for multiple workspaces.


Question

Hi all :wave:, we’re using a custom source connector which we’ve built using the connection builder in the UI (on Airbyte Cloud).
We want to use this in multiple workspaces and manage it in code if possible. We’re using Terraform for our resources but I can’t see how to manage the connector YAML in Terraform or via the API, has anyone been able to achieve this? Thanks


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-source-connector", "yaml", "terraform", "api", "multiple-workspaces"]
2

I’ve requested assistance from the platform team, <@U06MHHGQHQB>. If I understand correctly, the custom connector in Terraform is only accessible to OSS users who have the connector definition ID.

3

Hi <@U06MHHGQHQB> and <@U06UYSU43S7>, it is currently not possible to manage your custom connector definitions using Terraform or the API. As Marcos said, you can only create custom sources on them if they’re already available on your workspace and you have obtained their sourceDefinitionId.
However, you may be able to use the airbyte-ci to deploy your custom connector to other workspaces, but I have not tried that yet.

4

I also need to be able to share a custom connector between multiple workspaces in Airbyte Cloud. I’m interested in learning what options are available.