Hi all, • Is there any way that I can managed the configuration files with a git repository. ◦ Expecting that when I change the configurations files content and commit it to the git, then I can sync it into Airbyte container and it will works, no need zip or containers restart, • Also, where are those file stored? Maybe we could find some way to adapt if it feasible. For our use case, managing and version control setting is one of the crucial points, some of our team members are prefer some other tools due to its yml configuration style and CLI, but i don’t think Airbyte can’t also do the same thing, so i want to find a way. Thanks a lot

instead of file and git repository, there’s been discussion to put that into a DB here: https://github.com/airbytehq/airbyte/issues/3605 Maybe you can participate n the discussion to add your use case there?

I think adding config to database is great but having config and version control of that will lead you deploy airbyte easily on different envs: dev, prod, staging.

yes that is my point. • it seems to be much more efficient when you can modify the config file. • It also a plus for bulk adding and modifying config, • Also, will be a killing point since airbyte generated and validated the required input already, just need to duplicate and modify, way better than not knowing if the set config will working or not.

infra as code FTW 🙂

so mostly having an API for setting source/ destination/connection is what is required? getting them? that way they can be kept in source control

@Aditya Guru Airbyte already has an API to do that. Probably a easier way to create sources and connections based on files.