To version control Airbyte without using the Terraform provider, you can use the Octavia CLI. Here are the steps to get started: ### Prerequisites 1. Docker and Docker Compose: Ensure you have Docker and Docker Compose installed. 2. Airbyte Open-Source Instance: You need an Airbyte open-source instance running locally with Docker Compose. This tutorial uses Airbyte v0.40.18. 3. Postgres and BigQuery Instances: You need a Postgres instance or another source, and a BigQuery instance or another destination. You can follow the [Postgres replication](https://airbyte.com/tutorials/postgres-replication) and [Postgres to BigQuery](https://airbyte.com/tutorials/postgres-to-bigquery) tutorials to set these up. ### Bootstrap an Octavia CLI Project 1. Set Environment Variables:

bash     export OCTAVIA_ENABLE_TELEMETRY=True     export AIRBYTE_USERNAME=airbyte     export AIRBYTE_PASSWORD=password

2. Initialize the Project:

bash     mkdir airbyte-configuration && cd airbyte-configuration     octavia init

This will create the necessary directories and files:

plaintext     .     ├── api_http_headers.yaml     ├── connections     ├── destinations     └── sources

### Import Existing Airbyte Configuration If you have an existing Airbyte instance that you want to version control, you can import the configurations:

bash octavia import all

This will populate the directories with your current configurations:

plaintext . ├── api_http_headers.yaml ├── connections │   └── postgres_to_bigquery │       ├── configuration.yaml │       └── state_819c7684-d353-45a1-b2e7-5eb42d8461c0.yaml ├── destinations │   └── bigquery │       ├── configuration.yaml │       └── state_819c7684-d353-45a1-b2e7-5eb42d8461c0.yaml └── sources     └── postgres         ├── configuration.yaml         └── state_819c7684-d353-45a1-b2e7-5eb42d8461c0.yaml

### Version Control Your Configuration After editing the YAML configuration files, you can use Git to version control your Airbyte configuration:

bash git add . git commit -m "Version control Airbyte configuration"

### Apply Configuration to a Different Instance To apply these configurations to a different Airbyte instance, you can use the following command:

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

### Note While Octavia CLI is useful, it is an alpha unofficial CLI and won't be maintained. Airbyte has released an official [Terraform Provider](https://registry.terraform.io/providers/airbytehq/airbyte/0.1.0), which is recommended for long-term use. For more detailed steps and examples, you can refer to the [tutorial on version controlling Airbyte configurations](https://airbyte.com/tutorials/version-control-airbyte-configurations). By following these steps, you can effectively version control your Airbyte configurations without using the Terraform provider.