Hello, We run airbyte on an ec2 instance. I would like to know what the best way/best practice to save/export configuration and how can I re-import it? I saw this: https://airbyte.com/tutorials/version-control-airbyte-configurations - is this accurate/the right way?

Yes, the tutorial you found on [version controlling Airbyte configurations](https://airbyte.com/tutorials/version-control-airbyte-configurations) is indeed the recommended way to save, export, and re-import your Airbyte configurations. To save and export your configurations, you can use the Octavia CLI. If you have an existing Airbyte instance that you want to version control, you can get the configurations with the

octavia import all

command after you initialize an Octavia CLI project. This command will retrieve all sources, destinations, and connection configurations. You can then commit this to a Git repository. Here's how you can bootstrap an Octavia project and import all configurations:

bash octavia init octavia import all

When importing resources, Octavia overwrites the environment variables that you configured originally with the real value and replace secrets with '**********'. Given this limitation, you can still version control Airbyte configs, but you won’t be able to push this new configuration to a different instance without editing the secrets in the template and adding the environment variables that may change between instances. To apply these changes to a different Airbyte instance, you can use the

octavia apply

command:

bash octavia apply –airbyte-url <http://production.myairbyte.com> –force –airbyte-username YOUR_USERNAME –airbyte-password YOUR_PASSWORD

Please note that the export and import options were recently removed from the Airbyte UI. The recommended way now is to use the Octavia CLI to import/export your configurations as mentioned in this [forum discussion](https://discuss.airbyte.io/t/3487). Remember, Octavia CLI manages Airbyte Configurations as Code (CaC) and not Airbyte Infrastructure as Code (IaC). Thus, Octavia CLI cannot provision an Airbyte instance. It is mainly used for version controlling resource configurations, reviewing resource configuration changes, and copying resource configurations between Airbyte instances.