👋🏻 It's me again for the latest octavia-cli updates! 🎉 We just released the

import

and

get

commands (version 0.39.32)! With the

octavia import

you can now import a resource configuration you created from the Airbyte web console to an

octavia-cli

project. It simplifies the process of migrating an existing configuration to another Airbyte instance. It is also the go-to approach if you have manually created a source/destination/connection and you now want to manage it with the CLI. The

octavia get

command shall be considered as a helper command to retrieve the configuration of an Airbyte resource in JSON. This is useful if you want to retrieve information about a resource in a script. I'd like to give warm kudos to @gunu who contributed to these commands! I hope it was a nice collaborative experience for him. You are all encouraged to contribute to the tool. All the improvements planned are listed here. To benefit from these updates you need to upgrade Airbyte and

octavia-cli

to version 0.39.32. Here is a guide to upgrading Airbyte. To upgrade

octavia-cli

you can run

curl -s -o- <https://raw.githubusercontent.com/airbytehq/airbyte/master/octavia-cli/install.sh> | bash

If you encounter any bugs or need assistance using the CLI you are welcome on our forum and our team will try to provide support there.

@Augustin Lafanechere (Airbyte) This sounds amazing, thanks for the update! May I ask a clarification question, are you using the Airbyte-API to fetch these configs, or through which way you get the infos? I'm thinking of integration with orchestrators, such as dagster created a resource where they integrate with our API (see resource here). This feature would be highly valuable in the API as well, but I don't know enough, maybe it's already there or you fetch from there? Thanks for helping me understand 🙂.

We are fetching everything from Airbyte's API. You can indeed use

octavia get

from an orchestrator to fetch information about an Airbyte resource and act accordingly. (e.g. getting the connection id from the connection name)

Thanks so much for clarifying, that sounds like what I was looking for. I will need to read a bit more, especially in terms of using best-practice in using the cli vs API with an external tool such as airflow/dagster/etc.