Upgrading custom connector version in Airbyte

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

When trying to upgrade a custom connector version in Airbyte, the user is unsure if the upgrade was successful and still sees the old tag being used. They are looking for a way to have Airbyte detect when a custom connector is behind the current version and upgrade it in place without affecting the existing state.


Question

I have a custom connector I’ve imported from ECR. I pushed a new version that shouldn’t change anything requiring a reset. I wanted to upgrade it in place, and the way it seemed to be possible is just typing in the new version and clicking “change”. But I don’t see for sure whether it did anything, and I still see the old tag 0.1.90 everywhere else I see this connector being used.

I have a feeling this is not the correct way to do it. How can I get airbyte to detect that I’m behind the current version on a custom connector, and then upgrade it in place (for cases where that’s not going to destroy “state” etc)?


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.

Join the conversation on Slack

["upgrade-custom-connector", "airbyte", "custom-connector", "version", "upgrade-in-place"]
2

There may be bigger problems too actually. Just noticing that the sync status advanced area shows state as empty after running this connection. On my development machine where I’m on new airbyte, state works properly. I think I just need to bite the bullet and upgrade this client’s airbyte instance and fix anything that breaks. It’s getting painful to keep working in 0.4.32. Seems a lot has been refined since that release.