ErikV
07/22/2025, 9:39 AMkapa.ai
07/22/2025, 9:39 AMbash octavia init octavia import all
This will create a directory structure with YAML configuration files for each resource. You can then version control these files or use them to replicate your setup elsewhere. Note that secrets will be masked in the exported YAML, so you’ll need to update them before applying to a new instance. To apply the configuration to another Airbyte instance, you can use: bash octavia apply --airbyte-url <http://your-airbyte-instance>
Keep in mind that Octavia CLI is an alpha tool and Airbyte now recommends using their official Terraform provider for production use cases, but Octavia remains a practical option for YAML-based configuration backup and migration between instances [Version control Airbyte configurations with Octavia CLI](https://airbyte.com/tutorials/version-control-airbyte-configurations). If you are using Airbyte’s UI, there was previously an import/export feature, but it has been deprecated for security reasons. For full instance migration (including state and logs), you may also consider backing up and restoring the underlying Airbyte Postgres database, but this is a more advanced and less granular approach. In summary: Yes, you can back up your Airbyte connector configurations as YAML using Octavia CLI or manage them as code with the Terraform provider.