Hi all, I wanted to get the community's thoughts on this: My team and I have gotten to the point where we've developed several internally useful custom connectors and would like to check in some commits. We don't want to open PR's on the main airbyte repo because our connectors won't be broadly useful (really specific use cases at this point) and we're primarily a gitlab shop these days. Our current thinking is to run airbyte from the main repo and keep our custom connectors in a separate repo, then programmatically add them with octavia/ the api. Thoughts on using this pattern?

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

Just so you know, we would absolutely still welcome your connectors in the main repo, even if they are for specific use cases 🙂 it might be a lot of work to keep your fork up to date and ensure everything is compatible, and the official repo also has extensive e2e testing that each connector runs through before it is published.

Thanks @Sunny Hashmi!