William Kaper
10/07/2024, 12:23 PMPrzemysław Dąbek
10/07/2024, 12:44 PMactor_definition_version table there are docker_repository and docker_image_tag columns, and you can update them to "switch" between official version and version you have stored in public/private registry (I use AWS ECR as a registry for Docker images). As long as there is compatibility in handling connection's state, it shouldn't be any issues with "switching".Brian Mulh
10/07/2024, 11:24 PMactor_definition_version rather than updating the existing oneNatik Gadzhi
10/12/2024, 9:43 PMNatik Gadzhi
10/12/2024, 9:53 PMairbyte-ci connectors build with flags for a pre-release build. This would build the image from the current work tree code, mark it with the version in metadata + -dev.{sha} , and it would push the metadata of that version to metadata registry, just not mark it as latest. This in turn allows Airbtyte-server to ingest and use it when we later pin it.
2. Then, we use internal tools to pin the particular actor (connection) to the particular dev build, if we need to experiment with it (or customer requests early access to a patch)
3. Then, when the patch is mainlined in the next public connector release, we remove the version pin.
Now, this is very close to what @Przemysław Dąbek suggests.
Because by “we pin” I mean that we make a DB record mostly how he describes.
What would be good here:
1. Document this flow and describe how to pin and unpin
2. Document that airbyte-server has an api endpoint for this (allegedly?) and describe how you could use it instead of editing the database directly.
3. Perhaps provide a retool dashboard template that users could use to pin, or make the UI for this.