https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> i see "upgrade all" but where is "r...
# replication-ask-ai
b
@kapa.ai i see "upgrade all" but where is "refresh definitions" for sources in the open source ui?
k
The knowledge sources you provided only describe how to: - Manually refresh the source schema at the connection level via Connections → [connection] → Schema → “Refresh source schema”. [[Schema change](https://docs.airbyte.com/platform/using-airbyte/schema-change-management#manually-refresh-the-source-schema)] They do not mention a “refresh definitions” control for sources in the OSS UI, nor where it would be located, and they also don’t describe the “upgrade all” button you’re seeing. Because of that, I can’t reliably say where “refresh definitions” should appear in your current OSS version, or whether it has been removed/renamed. What you can do from the UI, per the docs, is: 1. Go to Connections. 2. Open a specific connection. 3. Go to the Schema tab. 4. Click Refresh source schema to pull the latest schema from the source. [[Schema change](https://docs.airbyte.com/platform/using-airbyte/schema-change-management#manually-refresh-the-source-schema)] If you’re specifically looking for a global “refresh definitions” for all source connectors (not per‑connection schema refresh), the knowledge sources don’t provide any information about that option or its current location.
b
no i mean a new version of the source connector was merged to main in github 5 days ago but i dont see it yet
@kapa.ai no i mean a new version of the source connector was merged to main in github 5 days ago but i dont see it yet
k
A message from kapa.ai
In Airbyte Open Source, new connector code merged to 
main
on GitHub does not automatically appear in your running instance. The knowledge sources indicate you need to: 1. Build/publish the new connector image For custom or updated connectors, you must build a new Docker image and make it available to your deployment (local registry, Docker Hub, etc.). [[Trouble updating low-code](https://discuss.airbyte.io/t/6622); [Developing locally 2.0](https://docs.airbyte.com/platform/2.0/contributing-to-airbyte/developing-locally#connector-contributions)] Example (from a similar Pardot case, but same idea):
Copy code
bash    docker build . -t airbyte/source-<name>:<tag>
Then push it to a registry your Airbyte instance can pull from. [[Pardot source](https://discuss.airbyte.io/t/605)] 2. Point Airbyte to that new image version In the OSS UI you update the connector’s Docker image tag / version: - Go to Workspace settings → Sources (or Destinations). - Find your connector and click the edit button. - Change the Default Version / Docker image tag to the new version you built/pushed. - Save. [[Custom connectors](https://docs.airbyte.com/integrations/custom-connectors); [Managing connector updates](https://docs.airbyte.com/platform/managing-airbyte/connector-updates#actions-to-take-in-response-to-connector-updates)] 3. Upgrade each existing source instance if needed Updating the catalog entry doesn’t automatically bump all existing sources; you upgrade them individually: - Go to Sources in the nav. - Open each source instance. - Click Upgrade and confirm. [[Updating custom connector](https://discuss.airbyte.io/t/5353); [Managing connector updates](https://docs.airbyte.com/platform/managing-airbyte/connector-updates#actions-to-take-in-response-to-connector-updates)] Because of this model, simply seeing a PR merged to 
airbytehq/airbyte
5 days ago is not enough for your OSS instance to use that version—you either need to: - Wait for an official connector image release that your instance pulls, and then change the version in Workspace settings → Sources, or - Build and use your own image as above. The knowledge sources do not mention any “refresh definitions” button that would pull the latest 
main
from GitHub into an existing OSS deployment, so I can’t point you to such a control.
b
how do i identify an official connector image release
3 Views
Open in Slack
PreviousNext
Powered by