950d24142a
Co-authored-by: Audrey Maldonado <audrey.maldonado@gmail.com> Co-authored-by: Alex <109167606+alex-gron@users.noreply.github.com> Co-authored-by: Jimmy Ma <gosusnp@users.noreply.github.com>
70 lines
2.6 KiB
Markdown
70 lines
2.6 KiB
Markdown
# Monday Migration Guide
|
|
|
|
## Upgrading to 2.0.0
|
|
|
|
Source Monday has deprecated API version 2023-07. We have upgraded the connector to the latest API version 2024-01. In this new version, the Id field has changed from an integer to a string in the streams Boards, Items, Tags, Teams, Updates, Users and Workspaces. Please reset affected streams.
|
|
|
|
## Connector Upgrade Guide
|
|
|
|
### For Airbyte Open Source: Update the local connector image
|
|
|
|
Airbyte Open Source users must manually update the connector image in their local registry before proceeding with the migration. To do so:
|
|
|
|
1. Select **Settings** in the main navbar.
|
|
1. Select **Sources**.
|
|
2. Find Monday in the list of connectors.
|
|
|
|
:::note
|
|
You will see two versions listed, the current in-use version and the latest version available.
|
|
:::
|
|
|
|
3. Select **Change** to update your OSS version to the latest available version.
|
|
|
|
### Update the connector version
|
|
|
|
1. Select **Sources** in the main navbar.
|
|
2. Select the instance of the connector you wish to upgrade.
|
|
|
|
:::note
|
|
Each instance of the connector must be updated separately. If you have created multiple instances of a connector, updating one will not affect the others.
|
|
:::
|
|
|
|
3. Select **Upgrade**
|
|
1. Follow the prompt to confirm you are ready to upgrade to the new version.
|
|
|
|
### Refresh schemas and reset data
|
|
|
|
1. Select **Connections** in the main navbar.
|
|
2. Select the connection(s) affected by the update.
|
|
3. Select the **Replication** tab. 1. Select **Refresh source schema**. 2. Select **OK**.
|
|
:::note
|
|
Any detected schema changes will be listed for your review.
|
|
:::
|
|
4. Select **Save changes** at the bottom of the page.
|
|
1. Ensure the **Reset all streams** option is checked.
|
|
5. Select **Save connection**.
|
|
:::note
|
|
This will reset the data in your destination and initiate a fresh sync.
|
|
:::
|
|
|
|
For more information on resetting your data in Airbyte, see [this page](/operator-guides/clear).
|
|
|
|
### Refresh affected schemas and reset data
|
|
|
|
1. Select **Connections** in the main navb nar.
|
|
1. Select the connection(s) affected by the update.
|
|
2. Select the **Replication** tab. 1. Select **Refresh source schema**. 2. Select **OK**.
|
|
:::note
|
|
Any detected schema changes will be listed for your review.
|
|
:::
|
|
3. Select **Save changes** at the bottom of the page. 1. Ensure the **Reset affected streams** option is checked.
|
|
:::note
|
|
Depending on destination type you may not be prompted to reset your data.
|
|
:::
|
|
4. Select **Save connection**.
|
|
:::note
|
|
This will reset the data in your destination and initiate a fresh sync.
|
|
:::
|
|
|
|
For more information on resetting your data in Airbyte, see [this page](/operator-guides/clear).
|