Hey everyone!! octavia wave We have a big news to share with you: octavia partyingoctavia partying our official Airbyte API and *Terraform Provider are both now available on Airbyte Open Source!* octavia partyingoctavia partying We will be sunsetting the unofficial alpha Configuration API by early 2024. Migrating to the Airbyte API should be relatively easy as many of the requests have a very similar set of required fields. The major difference between the Configuration API and the Airbyte API is that the Airbyte API provides a REST interface instead of the RPC style found in the Configuration API. If there are Configuration API endpoints your team relies on, that you are not seeing equivalents for in the Airbyte API, you can let us know by emailing riley@airbyte.io. Here is some more info about the API and Terraform Provider launch. If you want to help socialize the launch, don't hesitate to go on HackerNews and Reddit to upvote our post!

Amazing!

timely feedback! we were actually thinking about renaming the "Content Hub" as the "Blog" as it's just an industry standard

@John (Airbyte) I was able to deploy the Airbyte, but I am unable to figure out any working doc for the OSS deployment of the Airbyte for this,

@John (Airbyte) this is great news, we've been waiting for this for ages, biding our time with duct tape around Octavia. I took a quick look through the docs and I didn't immediately see any resources for custom destinations and sources. We have a number of connectors we've built and host in our private Docker repository. Is there any way to manage these through the terraform provider?

thanks, both. Let me involve our PM for the Terraform Provider to address your points, I think he's currently off, so might be a few days.

We have a number of connectors we've built

We've got the same issue with YAML connectors built with the low-code CDK

One bit that we like from the Config API is that it returns detailed error information when a job fails, will this be ported to the cloud api

btw, how do we access the OSS provider page? I only see the cloud provider in terraform registry

It is the same provider, you only need to specify a different server url: https://registry.terraform.io/providers/airbytehq/airbyte/latest/docs

@Eric Schrock > I took a quick look through the docs and I didn’t immediately see any resources for custom destinations and sources. We have a number of connectors we’ve built and host in our private Docker repository. Is there any way to manage these through the terraform provider? Custom connectors will be made accessible through the Airbyte API and Terraform provider. It is prioritized against other engineering work, but we are targeting to have this available this winter.

Are all of the existing connectors supported in Terraform or just the connectors listed in the Airbyte API docs? Asking because we're trying to create a source using DV-360 and not seeing it

> Are all of the existing connectors supported in Terraform or just the connectors listed in the Airbyte API docs? Asking because we’re trying to create a source using DV-360 and not seeing it @Emily Armstrong Today, only those listed in the Airbyte API docs. In September we are targeting to work on allowing for connector definitions to be listed through the Airbyte API, as well as within this Fall season to have enabled “custom connectors” (but really any connector definition id) to be used to create source/destinations. This could change based on roadmap priorities shifting, but that is the current plan right now.

@Riley Brook we use: https://cloud.airbyte.com/api/v1/jobs/get that returns the log lines - we then ship that to our logging platform'

With the OpenTofu version of Terraform currently. How does that impact this API.

Hey @Riley Brook, coming back to all this, when do you think custom connectors will be available in terraform ? Is there some board where we can track progress?

👋 In February we plan to have Custom Connectors available through Airbyte API & Terraform Provider for Cloud, OSS and Self-Managed.

That’s great news! Thank you 🙇 Is there any board/issue I can track to get updates?

Definitely Sebastien 🙂 Status can be tracked here ➡️ https://github.com/orgs/airbytehq/projects/37/views/1?pane=issue&itemId=45471174

hey @Riley Brook any update on this?

hi @Janeth! we do have a private channel with your team, would this be a better place?

Thanks @John (Airbyte) for replying. Let me give it another shot tomorrow with fresh eyes. I may try another source if GS isn't cooperating. If I am not successful I'll reach out and maybe you could add me to that team 🙂 I appreciate it.

👍