Hello! I am attempting to upgrade my Salesforce Connector to v2.8.0. It is available in an Airbyte instance that my team runs on v2.0.1. However, it is not available in an Airbyte instance that my team runs on v.2.1.0. Is the updated Salesforce Connector not available in the newer Airbyte version?

The knowledge sources don't contain specific information about why Salesforce connector v2.8.0 would be available in Airbyte v2.0.1 but not in v2.1.0. However, there are a few things worth noting that may help explain the situation: Airbyte v2.1.0 introduced significant changes Airbyte v2.1.0 replaced Helm chart V1 with Helm chart V2, and also replaced the

connector-builder-server

with a manifest server. [Airbyte 2.1 Notes] If your v2.1.0 instance was recently migrated or freshly deployed, it's possible the connector registry or local connector images haven't been fully synced yet. For self-managed plans, connector updates are opt-in On self-managed Airbyte, all connector version updates (major, minor, and patch) are opt-in via the settings page. You'll see a badge in the sidebar indicating available updates. [Connector Updates] Steps to check and update the connector on your v2.1.0 instance: 1. In the navigation bar, click Workspace settings > Sources (or Organization settings > Sources if on Self-Managed Enterprise). 2. Find the Salesforce connector in the list — Airbyte lists both the current in-use version and the latest version available. 3. Click Change to update to the latest available version. 4. Then update each individual source instance by selecting it and clicking Upgrade. [Connector Updates] If the connector image simply isn't available locally on the v2.1.0 instance, you may also need to manually pull it:

docker pull airbyte/source-salesforce:2.8.0

I'd recommend checking whether the connector registry is properly synced on your v2.1.0 instance, and if the issue persists, reaching out to the Airbyte community forum or Slack for further assistance, as the knowledge sources don't provide a definitive explanation for this specific discrepancy. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai - how would i go about checking whether the connector registry is properly synced?

I'm sorry, but the knowledge sources do not contain enough information to provide a reliable answer on how to check whether the connector registry is properly synced on a self-managed Airbyte instance. What I can suggest based on the available information: • The PyAirbyte

airbyte.registry

module provides some registry-related functions (like

get_connector_metadata

and

get_available_connectors

) that could help you inspect what connectors are available in the registry programmatically. [PyAirbyte Registry] For more specific guidance on diagnosing registry sync issues on a self-managed instance, I'd recommend reaching out through official Airbyte support channels: • Airbyte Community Slack • Airbyte Community Forum • Airbyte GitHub Issues 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Would it make sense that the Airbyte Salesforce connector v2.8.0 would work in Airbyte 2.0.1 but not Airbyte 2.1.0

The knowledge sources do not contain enough specific information to definitively explain why Salesforce connector v2.8.0 would work in Airbyte v2.0.1 but not v2.1.0. However, one thing worth noting is that Airbyte v2.1.0 is explicitly flagged as experimental: > "This version of Airbyte is experimental. Airbyte changed the way we assemble new versions and haven't tested every feature and Helm chart configuration in version 2.1.0." [Airbyte 2.1 Notes] So it's plausible that connector availability or registry behavior could be affected by the experimental nature of that release. Additionally, v2.1.0 introduced significant architectural changes (Helm chart V2 only, manifest server replacing connector-builder-server) that could potentially impact how connectors are loaded. [Airbyte 2.1 Notes] Given the experimental status of v2.1.0, I'd strongly recommend raising this directly with Airbyte through: • Airbyte Community Slack • Airbyte GitHub Issues They would be best placed to confirm whether this is a known issue with v2.1.0. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.