You can back up your Airbyte configurations (sources, destinations, connections) using the Octavia CLI, which is a command line interface provided by Airbyte. This tool uses the Airbyte API under the hood and allows you to manage resource configurations as code in YAML format. Here's how you can do it: 1. First, you need to import all existing resources on your Airbyte instance. You can do this with the

octavia import all

command. This will create local configuration files for all Airbyte resources that were already existing on your instance.

bash $ octavia import all

After running this command, you should see a message indicating that the import was successful for each of your sources, destinations, and connections. 2. Please note that any secret values that exist in these configuration files are not imported, so you will need to manually update these in the configuration files. 3. Once you have these configuration files, you can reinstall Airbyte and then use the

octavia apply

command to apply these configurations to your new Airbyte instance. For more detailed instructions, you can refer to the [Octavia CLI documentation](https://docs.airbyte.com/cli-documentation) and the [tutorial on version controlling Airbyte configurations](https://airbyte.com/tutorials/version-control-airbyte-configurations). Please note that this process requires you to have the Octavia CLI installed and configured to target your Airbyte instance. If you haven't done this yet, you can find instructions in the [Octavia CLI README](https://github.com/airbytehq/airbyte/blob/master/octavia-cli/README.md).

I feel like I cleared everything out using docker prune, but for some reason airbyte is failing to start and temporal is complaining about

Unable to create dynamic config client. Error: unable to validate dynamic config: dynamic config: config/dynamicconfig/development.yaml: stat config/dynamicconfig/development.yaml: no such file or directory

it keeps looping through these messages:

@Igor Safonov, good find, I'm trying that out now

kind of worked, but not it's throwing different errors...

Ok, I think I managed, for some reason the file that I downloaded from github was in json format...

Thanks for the help @Igor Safonov

(I am using Google VM Instances to configure airbyte)