User has a question about Connector Builder/Low Code
x-posting here as it is a question about Connector Builder/Low code https://airbytehq-team.slack.com/archives/C021JANJ6TY/p1714053044889399
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.
<@U069EMNRPA4> No, this is in our OSS deployment (k8s via Helm) currently. Oddly enough, I can only make tests work by manually changing the manifest version in YAML mode (to match the 0.79.1), but I can only make the connector work in production by exporting it from the UI mode without changing the manifest version (so it stays at 0.83.0). This makes it very painful to develop connectors, since every time I add something I need to flip to YAML mode and change the manifest version to test.
Is there a clean way to upgrade source-declarative-manifest without it getting blown away by upgrades via Helm? It’s odd to me that they would be out of sync in a virgin deployment to start with—so I agree that it would be much nicer for them to be synced with each release.
So the test reads are broken unless your manifest says 0.79, but production image runs with 0.83 but not 0.79? Dammit.
We know what it is and we’re working on it. We will finally do proper semver. This was the last drop.
Re: helm: I need to take a look, but I don’t think helm should have the last word in what connectors and what versions you’re running.
Anyway, it will take 1-3 weeks but we’re on it.
<@U069EMNRPA4> Awesome, really appreciate you looking into this and sounds like it’ll help a lot going forward.
On the Helm side, I’d agree since it’s a connector—but I also see that this one is treated specially since it isn’t actually IN the connector list so wasn’t sure if it was part of the base container. Is there a reason that it isn’t just another connector that can be up/down-graded like others? Is it just because you can’t use it directly or because it’s a dependency of Builder, or is there more to it than that?
Just hit seemingly the same problem, version 0.61.0. Are there workarounds?
<@U035912NS77> that’s not great.
Are you using a cloud workspace? Can you link me to your workspace / connector to try it out?
The error about manifest being greater than connector means that your web UI knows that the latest CDK version is 0.83, BUT your cluster is running source-declarative-manifest that is a few versions behind. We auto-deploy new versions on Cloud, but not on OSS — we should include this in our semver work, cc <@U033JKD3W8G> and <@U047ANT3J84>