How to handle versioning and migration in Airbyte OSS?
Hello
we are working with Airbyte OSS and we need to versionning and migrate to the new versions so any idea ?
thnks in advance
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
What do you mean by “we need to versioning and migrate to the new versions”?
Hi Justin and thks for reply,
As part of our work with Airbyte OSS, we’ve created numerous connections and custom connectors. However, when there’s an upgrade to a source or destination, manually executing the upgrade process often leads to errors and instances crashing. To address this, we want to preserve all our existing connections and custom connectors so that we can use them on other deployed instances. Additionally, we need a solution to upgrade all Airbyte instances efficiently and maintain a clean environment.