Hi I have created some custom sources and added th...
# help-api-cli-orchestration
v
Hi I have created some custom sources and added them through the Airbyte UI
settings >> Sources >> New connector
Can I include them via Octavia CLI? or any other way without using UI
j
Yes, you can include custom sources via Octavia CLI. To do so, you will need to get the source ID for the source. You can run the command
octavia list connectors sources
to get the connector ID. For example, if you have a Postgres source, you can run
octavia list connectors sources | grep postgres
to get the source ID. Once you have the source ID, you can bootstrap the source with the
octavia generate source
command. For example, if the source ID is
decd338e-5647-4c0b-adf4-da0e75f5a750
, you can run
octavia generate source decd338e-5647-4c0b-adf4-da0e75f5a750 postgres
to bootstrap the Postgres source. The CLI will create a
postgres
folder under sources with a
configuration.yaml
file. You can then edit the configuration and run
octavia apply
to apply the changes. For more information, please refer to the

Octavia CLI tutorial

and the CLI documentation.
v
Hi, @Jerri Comeau (Airbyte) Thanks for your response, but unfortunately its not working. Im generating a new image with this command
docker build ./airbyte-integrations/connectors/<connector-name> -t airbyte/<connector-name>:dev
If I run
octavia list connectors sources
it is not getting listed Until i go to airbyte UI and add it settings >> Sources >> New connector Is there a way to add via CLI?
j
@Jerri Comeau (Airbyte) I think what you’re describing works for Airbyte, but not for custom connectors, which @Vivek PG is asking about. Would also be curious to learn how custom connectors are integrated w/o GUI.
v
Hi @Jerri Comeau (Airbyte), @jan I found a way to do this via the API....But not able to do this via Octavia CLI. POST METHOD URL:
Copy code
localhost:8000/api/v1/source_definitions/create_custom
BODY:
Copy code
{
  "workspaceId": "153f0a47-6ace-4976-ac95-0adeeaa13ea5",
  "sourceDefinition": {
    "name": "TEST_sonarcloud",
    "dockerRepository": "airbyte/source-sonar-cloud2",
    "dockerImageTag": "devel",
    "documentationUrl": ""
  }
}
Reference: https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#post-/v1/source_definitions/create_custom
j
Hi @Vivek PG thanks for the follow up, found the API as well. Bummer the CLI isn’t on par.