Using custom sources and destinations in Terraform

Summary

Moving setup from Octavia to Terraform, having trouble with custom sources and destinations in Airbyte. Terraform seems to only work with existing sources and destinations. Referenced GitHub issue #36 for discussion.


Question

Hello everyone, we’re thinking about moving our setup from Octavia to Terraform. But we’re having trouble using custom sources and destinations that we set up in Airbyte.
Right now, we make a source from a Docker container and get its UUID through an API, which we use in Octavia. It looks like Terraform only works with sources and destinations that are <Terraform Registry there>.
I found a https://github.com/airbytehq/terraform-provider-airbyte/issues/36|discussion about this problem on GitHub, but I just want to make sure that’s really the case.



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

["octavia", "terraform", "custom-sources", "custom-destinations", "airbyte", "api", "docker-container", "github-issue"]