Hello, we have been using Airbyte for a few months, we are wondering about the good practices you have on the administration of the connections and the parameterization because we regularly have problems to follow the modifications of a member of the team on the UI. We wonder if we should only use the API to define the connections and follow the modifications via our repo on Gitlab. Do you have any feedback on this usage? What do you think about it ? Thanks

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 3007 to ensure timely resolution!

Hey @Fabrice Simon, Thanks for the question. We don’t really have any guides on best practices for managing airbyte within an organization. That being said, based on what you suggested, managing the connections via our API and using a commit history to record modifications seems to make sense to me. How many connections does your organization manage?

hey, thanks for you answer, today we have one connection per table of a postgre database because we need to launch only one specific table refresh and not the entire pool of tables. So it can be difficult to administrate when the number of tables increase

Thanks for the additional context. If the primary concern is managing the number of tables and each of your connections represents a table of your postgres database then the API should be a good way to manage everything. Let us know if you run into any issues.