I am curious; Is there value in using Octavia CLI to export workspace JSONS to check into version control if we’re deploying Airbyte with an external app DB?

Do you snapshot your external DB? Do you want the ability to rebuild things from scratch if you have to? It's the latter that drove us to octavia - we can bring up a completely fresh database and a new airbyte deployment, and get to where things are now in minutes, sans state of course (so, we'd just need to reset our connections and do new full syncs). Of course not something we plan to do frequently, but it's nice to know that we can.

Good answer, thanks @Adam Bloom. So, are you exporting the JSON and checking them into version control? Are you importing your configs into Airbyte via Octavia as well?

No, not exporting anything. Rather, octavia yamls are the source that we load into airbyte. They, along with our encrypted secrets via sops, are checked into version control.

Got it, I guess I’m confused where these Octavia YAMLs come from. Our Airbyte instance has two connections already setup (in both dev and prod), but when

octavia get connection

, etc, it only generates JSON

yeah,

octavia import

will generate them. I did this before that command existed, so a combo of

octavia generate

and some trickery to convince octavia that these were existing resources and not new ones

Thank you very much @Adam Bloom for these insights, I’m glad you are using it for this kind of use case. @Dustin Shapiro do you have additional questions?

Nah, I think he covered it! Thanks again