Hello. I am running airbyte locally and looking to write a bash script which will install and run airbyte along with my custom sources. I’m not able to find a way to add a connector source programatically. If I have the local docker image installed and the minimum needed information for the custom source, it seems there should be a way to install airbyte with a customer connector from a bash script. The documentation seems to indicate the only way to add a custom source locally is by adding the connector manually in the UI. Is this really the case? It seems like there should be a headless way to install a connector source from a docker image programatically.

Based on the information provided in the extracts, it appears that the primary method for adding a custom connector to Airbyte is indeed through the UI. However, once the connector is added, it can be used both from the UI and Airbyte's API ([source](https://docs.airbyte.com/integrations/custom-connectors/)). To add a custom connector, you need to have the Docker coordinate of the custom connector from Dockerhub or any image repository that Airbyte can access. In the UI, you go to the Admin section, click on

[+ New connector]

on the top right, and provide the necessary information ([source](https://docs.airbyte.com/integrations/custom-connectors/)). For local development, you can build the Docker image for your connector and then use it in your local Airbyte instance. The built Docker image must be accessible to the

docker

daemon running on the Airbyte node ([source](https://docs.airbyte.com/connector-development/tutorials/cdk-tutorial-python-http/use-connector-in-airbyte)). However, the extracts do not provide information on how to add a connector source programmatically without using the UI. It might be possible to do this using Airbyte's API, but the extracts do not provide enough information to confirm this or provide instructions on how to do it. For more detailed information, you might want to refer to the [Airbyte documentation](https://docs.airbyte.com/) or ask in the [Airbyte community](https://airbytehq.slack.com/).

Right, so it seems like this isn’t possible. Airbyte team, wondering if this is a feature you have ever thought to implement? If one wanted to establish an end-to-end ephemeral deployment, it seems like requiring the user to interact with the UI is not ideal.