octavia rocket octavia-cli updates octavia rocket 🎉 Merged : The commands to list connectors and workspaces sources/destination/connections are now available: •

octavia list connectors sources

•

octavia list connectors destinations

•

octavia list workspaces sources

•

octavia list workspaces destinations

•

octavia list workspaces connections

👀 Ready for review : We opened the PR for the

octavia init

command, which will create the directory architecture for your project. Community reviews are welcomed! Next steps: Implement

octavia create

to generate configuration file according to connectors specification. This will be the first key feature for this tool! We know that the current project state is very early and not usable as most of the features are missing, but feel free to try it out and give feedback! You'll find attached some screenshots of the outputs of the commands mentioned above.

hi airbyte devs I am impressed by the level of detail provided in the execution plan.. is there an example for the YML defintion of a octavia source + destination?

hi team, I'm trying to build octavia but after 4 or 5 errors I managed to cut through, I'm now stuck with something I can't find a solution to anywhere, anyone seen this one before?

> Task :airbyte-db:jooq:generateConfigsDatabaseJooq FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':airbyte-db:jooq:generateConfigsDatabaseJooq'.
> Process 'command '/usr/lib/jvm/java-17-oracle/bin/java'' finished with non-zero exit value 255

Hi team, Airbyte connectors have versions and they aren't automatically updated https://docs.airbyte.com/integrations/custom-connectors#upgrading-a-connector. Are there plans to add this functionality to octavia cli in the future?

octavia rocket octavia-cli updates octavia rocket Hello dear Octavia followers! I'm very excited to share that we will soon have the tool ready for an official alpha release🎉! I'm looking for a couple of alpha testers to ensure no critical bug is hidden in the codebase before the release. Are some of you interested in trying to install and use the tool and share feedback with me? Feel free to reach out in the thread if you're available this week. The CLI is still alpha, and some features are not yet implemented; feel free to track the planned additions in our Github issues.

Hey 👋 I’m going to present Octavia at 10 PST on our YouTube channel for the launch week live stream.

<!here> we’re live on:

Shouldn’t we be able to do:

octavia generate source postgres my_db

which would do behind the scenes: •

octavia list postgres

• and automatically translate that into its definition id if it finds one match • if multiple, it can ask to select one from the list for example (or just print a warning/error)?

What was the surprise?) I haven’t seen any links in the stream 😞

https://airbyte.com/blog/airbyte-acquires-grouparoo-to-accelerate-data-movement]

Sorry about that @Artyom Giletich Here is the link. I posted it but it might have gotten blocked.

Hey folks, I was referred to this channel with a question about whether anyone has started work toward a Terraform module for managing connections as code. Anybody working on something like that?

y\

Hey! Is Octavia expected to work for Airbyte instances hosted on EKS?

Hi, quick question - is there a minimum version of airbyte that octavia-cli can connect to? I am able to test and connect locally on my dev airbyte instance (latest). However, when I create an ssh tunnel to my prod instance and expose on localhost:8000 I get an error: Error: Could not reach your Airbyte instance, make sure the instance is up and running and network reachable: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/v1/health (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f30585704f0>: Failed to establish a new connection: [Errno 111] Connection refused')) The prod server airbyte version is a bit old 0.30.16-alpha

Hi all, wondering if octavia command can support adding a source / destination by reading from a pre-defined one (by other connections)? Is there any example to do so?

Hi all, wondering if octavia command can support removing a pre-defined source / destination / connection? Is there any example to do so? I tried to delete from the UI but looks like the removal is not complete, and also did not find any command line to support deletion.

Any support for setting normalization via octavia?

Hi all, cli is very usable now, great work @Augustin Lafanechere (Airbyte) ! I am having trouble migrating embedded service credentials to ~/.octavia env file. What is the proper way of doing it regarding multiline eg gcp service json keys? Is it just base64 encoding the contents of the json file? Some example in the docs would be nice

Suggestion for the generated connections yaml regarding setting up streams and primary keys to just provide an example in the comments - i was having a hard time figuring out the proper format eg [ [field1], [field2], ...,[fieldN] ]

I have just started to try using octavia on the Mac. I have been following the directions on the video - I have run octavia init and it creates the (empty) directories. octavia list connectors destinations works - I get a list of connectors. However, when I try: octavia generate destination 4816b78f-1489-44c1-9060-4b19d5fa9362 s3 🐙 - Octavia is targetting your Airbyte instance running at http://localhost:8000 on workspace 80aad121-ae3f-43da-81d8-b41a4b79d424. Error: Definition 4816b78f-1489-44c1-9060-4b19d5fa9362 does not exists on your Airbyte instance. What am I missing? Thanks…

Hi Is it possible to define a Manual Replication frequency through Octavia CLI (in the Yaml file) like it’s possible with the web UI ?

is there a way to generate all the necessary configurations for an existing airbyte configuration? e.g. automatically generate all source + destination + connector yaml files? the cli seems to generate each object individually and doesn’t create from existing or a simper solution for now: how can I convert the airbyte export configuration into yaml format that octavia-cli works with

This message was deleted.

👋🏻 Hey dear octavia-cli power users, I'd like to give you some updates about the recent progress made on the CLI: • You can now enable normalization / DBT custom transformation from a connection's

configuration.yaml

file. (PR) • You can now deploy a connection on multiple Airbyte instances. This was problematic because

configuration.yaml

referenced source and destination id that are different on each instance/workspace. (PR) • You can now set custom HTTP headers to be sent to Airbyte. This can be useful if you have a custom authentication mechanism in front of Airbyte. It is also a great step to ensure the CLI compatibility with Airbyte Cloud in the future when our public API will be released. (PR) To benefit from these updates you need to upgrade Airbyte and

octavia-cli

to version 0.39.19. 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

Our current efforts are focused on implementing a

get

and

import

command to pull an already existing Airbyte resource (source/destination/connection) to a local octavia project. Kudos to @gunu for this PR initiative!

👋🏻 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.

I’m looking to deploy Octavia-CLI along with Airbyte, and am not sure the best way to carry this out. I’m deploying Airbyte to K8s using a Helm Chart. Octavia seems to only be available as a Docker image, so I am not 100% sure the best method to take to integrate it into the deploy. Sorry, I’m new to the infra side, so appreciate any feedback.

👋 I am getting an error when attempting to generate YAML for workspace connections, as well as import commands.

octavia import all

🐙 - Octavia is targetting your Airbyte instance running at <http://airbyte-webapp:80> on workspace c4612f46-8290-46d2-8975-080f46fd8cff.
Error: Definition decd338e-5647-4c0b-adf4-da0e75f5a750 does not exists on your Airbyte instance.

The weird thing is, is I can run

octavia list workspace sources

and it will return my sources. If I take that source_id and pass it into a a get or import, it displays the above error 🤷

Hi! I am implementing a devops pipeline with octavia on our company and I just thought it would be an interesting idea to have source definitions also be deployed by octavia. I thought of it because of two reasons: 1. It would be easier to create source definitions for custom conectors in one place and just have octavia apply it 2. Sources that reference custom source definitions have to replace the definition id (at least until https://github.com/airbytehq/airbyte/issues/10981 gets implemented) on multiple airbyte instances, because UUID for them is different. This would be the same solution as connections reference the source directly instead of the source uuid. Would this be a good solution/possible? Is there a better way to deploy custom conectors on devops?