Best practice for preventing configuration settings loss when upgrading self-hosted Airbyte instance

Summary

When upgrading a self-hosted Airbyte instance, users may lose configuration settings in the .env and docker-compose.yml files. What is the best practice to prevent this?


Question

When upgrading a self-hosted airbyte instance using the guide: https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-on-docker I loose all my configuration settings in the .env and docker-compose.yml files. What is best practice in preventing this?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["self-hosted", "airbyte-instance", "upgrade", "configuration-settings", "best-practice"]