Connector versions management via CICD

Hey there 👋 ! Is there any simple way to manage the connector versions via a versionned config file deployed through CICD pipeline, instead of using the Admin UI and clik on `change`/`Upgrade All` ? This part of the doc looks interesting but only refers to resource management

New message text here

I mean the source connectors, not the connector instances which connect source and destination objects.

Yes, there are a couple of ways to override the

oss_registry.json

in Airbyte. Method 1: Edit the registry by hand You can download the current registry from [here](https://connectors.airbyte.com/files/registries/v0/oss_registry.json) to somewhere on your local machine and make the necessary changes. Method 2: Use the registry generator You can follow the steps in the [Metadata Orchestrator Readme](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/metadata_service/orchestrator/README.md) to set up the orchestrator. After setting up, you can use the public GCS url of the registry created by the orchestrator to point the platform to the modified registry. Here's how you can do it:

bash REMOTE_CONNECTOR_CATALOG_URL = <url of the modified registry>

Also, when the

metadata.yaml

file is updated, this data is automatically uploaded to Airbyte's metadata service. This service then generates the publicly available

oss_registry.json

and

cloud_registry.json

registries based on the information provided in the

registries

section. For instance, if a connector is listed as

enabled: true

under the

oss

section, it will be included in the

oss_registry.json

file. Sources: - [Testing a local catalog in development](https://docs.airbyte.com/connector-development/testing-connectors/testing-a-local-catalog-in-development) - [Connector Metadata.yaml File](https://docs.airbyte.com/connector-development/connector-metadata-file)