Connector Builder UI Documentation

Connector Development
1

I am trying to create a new connector using the UI, but the documentation on what to do with the exported yaml seems to be either incorrect or outdated or I am just confused.
I am following Connector Builder UI | Airbyte Documentation. I start to have issues in the “Exporting the YAML” section, when it talks about overwrite the contents. It references a yaml file with the name of the connector but I don’t get a file like that I get a manifest.yaml.
I used the connector generator talked about in this doc: Step 1: Generate the source connector project locally | Airbyte Documentation. I am able to follow step 1 and 2 without issues but I get lost in step 3 when it talks about a yaml file with same name as the connector, again I just have a manifest.yaml where the named file should be. If I take the content of the yaml from the UI builder and put it in manifest.yaml I get a successful connection when I run main.py check.
In step 4 it talks about creating schema files, but doesn’t reference how to use the schema built in the UI builder.

Is there any documentation for the UI Builder connector process, or anything I am missing?

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

There is a schema tab in the stream editor. There you can specify the json schema. When you export the yaml file it has converted the json schema to a yaml structure inline in the manifest.yaml.
Regarding the naming of the connector definition yaml file, when running the connector generator I also get a manifest.yaml and that is where you define your connector. The documentation is probably lagging. There is rapid development of this right now I guess and documentation has to catch up when this settle.