Hey everyone 👋 The frustration with the Octavia CLI is known, and we intend to get things back to a better state this year 🙂 @Dayten Sheffar @Eric Schrock The team who owns the Octavia CLI at Airbyte also owns additional critical projects that have been the priority over the last 8 months. This team has not had the capacity to implement fixes or improvements due to other project priorities. This year, Airbyte will get to the point where we do have that capacity. You can look forward to improvements to the CLI coming over the 2nd-half of this year 🙌

Thank you - improvements in automation and orchestration are sorely needed to be able to operate Airbyte in any robust fashion. Althrough given the choice, I'd happy throw all of our CLI automation in favor of a terraform provider!

@Eric Schrock For your use case - what value is unlocked by using a terraform provider, compared to using a CLI? (assuming both are in ideal working states)

We use terraform for everything, so it's generally preferable. But more than that, it solves a lot of problems that a custom-built CLI wouldn't have. For example: • Centralized state management • The ability to plan to see changes before they're applied • Github pull request integration • Atlantis monitoring and management • Native IDE support • Ability to create modules • Pull parameters from different secure mechanisms I'm sure there are more that I'm forgetting. Plus it creates a single tool for managing all the infrastructure, from the EC2 instance to the connectors installed to the configuration deployed. Right now the CLI is awful trying to keep things in sync, etc. Even with the bugs fixed, we'd have to re-create all of the above around a different tool. This also doesn't cover the fact that we want to only control the platform through automation. We need RBAC so that we can have automation users only able to make changes, with regular users only able to view and trigger jobs.

That is super helpful - thank you for taking the time Eric 🙌