Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix version in intermediate bump #8069

Merged
merged 1 commit into from
Nov 17, 2021
Merged

fix version in intermediate bump #8069

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/operator-guides/upgrading-airbyte.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,18 +12,18 @@ If you are running [Airbyte on Kubernetes](../deploying-airbyte/on-kubernetes.md

## Mandatory Intermediate Upgrade

**If your current version of airbyte is < v0.32.1-alpha, you first need to upgrade to this version before upgrading to any later version.**
**If your current version of airbyte is < v0.32.0-alpha, you first need to upgrade to this version before upgrading to any later version.**

The reason for this is that there are breaking changes made in v0.32.1-alpha, and the logic for these changes is removed in later versions, making it impossible to upgrade directly.
To upgrade to v0.32.1-alpha, follow the steps in the following sections, but replace the `docker pull` or `wget` commands with the following:
The reason for this is that there are breaking changes made in v0.32.0-alpha, and the logic for these changes is removed in later versions, making it impossible to upgrade directly.
To upgrade to v0.32.0-alpha, follow the steps in the following sections, but replace the `docker pull` or `wget` commands with the following:

1. If you are in a cloned Airbyte repo, v0.32.1-alpha can be pulled from GitHub with
1. If you are in a cloned Airbyte repo, v0.32.0-alpha can be pulled from GitHub with

```
git checkout v0.32.1-alpha
git checkout v0.32.0-alpha
```

2. If you are running Airbyte from downloaded `docker-compose.yaml` and `.env` files without a GitHub repo, run `wget -N https://raw.githubusercontent.com/airbytehq/airbyte/v0.32.1-alpha/{.env,docker-compose.yaml}` to pull this version and overwrite both files.
2. If you are running Airbyte from downloaded `docker-compose.yaml` and `.env` files without a GitHub repo, run `wget -N https://raw.githubusercontent.com/airbytehq/airbyte/v0.32.0-alpha/{.env,docker-compose.yaml}` to pull this version and overwrite both files.

As a warning, this upgrade requires specs to be retrieved for all connectors that currently exist in your database. So, if specs cannot be retrieved for any of your connector images, server startup will fail. In this case you must either fix the image so that spec retrieval is successful, or set the `VERSION_0_32_0_FORCE_UPGRADE` environment variable to `true`, which will cause the server to delete any connectors for which specs cannot be retrieved, as well as any connections built on top of them.

Expand Down