We’re planning on deploying airbyte to our VMs and we a way to configure airbyte sources, destinations, and connectors programmatically, i.e. through an API or a config file. Is such a thing supported? 🤞

Yes, Airbyte supports programmatically configuring sources, destinations, and connectors. There are a couple of ways you can achieve this: 1. Airbyte API: The Airbyte API is a reliable, easy-to-use interface for programmatically controlling the Airbyte platform. It enables users to control Airbyte programmatically and use it with orchestration tools like Airflow. You can find more details about the API in the [API documentation](https://docs.airbyte.com/api-documentation). 2. Octavia CLI: Octavia CLI is a command-line tool that allows you to configure Airbyte resources. With Octavia CLI, you can bootstrap a project, import the configuration of an existing instance, create source and destination configurations in YAML, edit YAML configuration files, and apply configurations to a different instance. However, please note that Octavia CLI is an alpha unofficial CLI that won't be maintained. Since the publication of the tutorial, Airbyte has released an official [Terraform Provider](https://registry.terraform.io/providers/airbytehq/airbyte/0.1.0), which is advised to use instead of the CLI. You can learn more about Octavia CLI in this [tutorial](https://airbyte.com/tutorials/version-control-airbyte-configurations). 3. YAML Configurations: You can define configurations in YAML programmatically. This is particularly useful when you have more connections, or your connections contain several Airbyte streams (database tables or API endpoints). Remember, no actual data from the source (or destination) connectors ever transits or is retained in the internal database. If you need to interact with it, for example, to make back-ups or perform some clean-up maintenances, you can also gain access to the Export and Import functionalities of this database via the API or the UI. Please note that you can also build a new connector in Java or Python using the templates provided by Airbyte. You can learn more about connector development [here](https://docs.airbyte.com/connector-development).

Thank you. I was wondering if its possible to configure a low-code connector through the API? 😄

Based on the information provided in the extracts, it appears that the low-code connectors in Airbyte are primarily configured through a YAML file or via a connector builder UI. The process involves generating API keys or credentials, setting up the project on your local machine, defining the connector YAML manifest, specifying stream schemas, and adding the connector to the Airbyte platform. Here is a brief overview of the process: 1. Generate the API key or credentials for the source you want to build a connector for. 2. Set up the project on your local machine. 3. Set up your local development environment. 4. Use the connector builder UI to define the connector YAML manifest and test the connector. 5. Specify stream schemas. 6. Add the connector to the Airbyte platform. For more detailed instructions, you can refer to the [Getting Started tutorial](https://docs.airbyte.com/connector-development/config-based/tutorial/getting-started) or the [video tutorial](). However, there is no mention in the extracts about configuring a low-code connector directly through the API. If you need more information or assistance, you might find it helpful to join the #help-connector-development Slack channel or contact Airbyte directly at feedback@airbyte.io. Sources: - [Low-code connector development](https://docs.airbyte.com/connector-development/config-based/low-code-cdk-overview) - [Connector Builder UI](https://docs.airbyte.com/connector-development/connector-builder-ui/overview)