Hello, is it possible to track the airbyte connector versions as code? I can see the configuration api has the ability to update a source definition docker image tag, but wondering is there way to store this information as part of the airbyte helm deployment?

Based on the information provided in the extracts, it seems that Airbyte does not currently support tracking connector versions as part of the Helm deployment. The connector versions are typically managed within the Airbyte UI or via the Configuration API, where you can update the source definition Docker image tag. However, you can manually manage the versions of your connectors by following these steps: 1. Bump the version in the

Dockerfile

of the connector (

LABEL io.airbyte.version=X.X.X

). 2. Bump the docker image version in the

metadata.yaml

of the connector. 3. Submit a PR containing the changes you made. 4. One of Airbyte maintainers will review the change in the new version and make sure the tests are passing. 5. You or an Airbyte maintainer can merge the PR once it is approved and all the required CI checks are passing. 6. Once the PR is merged the new connector version will be published to DockerHub and the connector should now be available for everyone who uses it. [source](https://docs.airbyte.com/connector-development) For custom connectors, you can add them to the Airbyte UI by providing the Docker coordinate of the custom connector from Dockerhub (or any image repository that Airbyte can access). [source](https://docs.airbyte.com/integrations/custom-connectors) As for storing this information as part of the Airbyte Helm deployment, it seems that this feature is not currently supported. However, you can upgrade your Airbyte deployment via Helm by changing the

version

parameter on your

values.yaml

and performing a Helm upgrade. [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1673825128446569) Please note that these are manual steps and may not fully meet your requirement of tracking connector versions as code. You might want to consider submitting a feature request to the Airbyte team for this functionality.