Skip to content

Add note about orphaned Airbyte configs preventing automatic upgrades #4709

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

Merged
merged 3 commits into from
Jul 16, 2021
Merged

Add note about orphaned Airbyte configs preventing automatic upgrades #4709

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fe38140
Add note about removing orphaned Airbyte configs
Jul 12, 2021
23219e5
Remove excess baggage
Jul 12, 2021
eb7daab
Add a resetting section to make this more clear.
Jul 15, 2021
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
4 changes: 4 additions & 0 deletions docs/operator-guides/upgrading-airbyte.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ If you are running [Airbyte on Kubernetes](../deploying-airbyte/on-kubernetes.md
docker-compose up
```

{% hint style="info" %}
If you did not start Airbyte from the root of the Airbyte monorepo, you will need to still need to manually remove these now orphaned Airbyte configurations. You can do this with `docker volume rm $(docker volume ls -q | grep airbyte)`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now, we don't have a section about how to reset an Airbyte instance to scratch anymore...

This command is equivalent to docker-compose down -v but it is more "global". Which means, it deletes all previous configuration of Airbyte (this one, regardless of where they were created from). There used to be a warning about this in the docs too.

Maybe @subodh1810 has more input on how to phrase this hint back better regarding to the automatic update?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I understand what it does, I think I just need to be more clear that it’s removing all of the user’s data. Maybe I can add its own section instead of having just a hint - I just don’t want to make it seem like a normal workflow, since it shouldn’t be anymore.

{% endhint %}

## Upgrading on K8s (0.27.0-alpha and above)

If you are upgrading from (i.e. your current version of Airbyte is) Airbyte version **0.27.0-alpha or above** on Kubernetes :
Expand Down