Rafael Felipe
12/23/2025, 1:24 PMkapa.ai
12/23/2025, 1:24 PMairbyte repo on GitHub. 2. Clone your fork and enter the repo: bash git clone [email protected]:{YOUR_USERNAME}/airbyte.git cd airbyte [[Developing locally 2.0](https://docs.airbyte.com/platform/2.0/contributing-to-airbyte/developing-locally#connector-contributions)] 3. Build the connector image (example for a source connector): bash airbyte-ci connectors --name source-mongodb-v2 build This produces a local Docker image tagged airbyte/source-mongodb-v2:dev. [[Developing locally 2.0](https://docs.airbyte.com/platform/2.0/contributing-to-airbyte/developing-locally#connector-contributions)] 4. Load and use this image in your local Airbyte instance (via abctl and UI version override) if you want to test it through the UI. [[Developing locally 2.0](https://docs.airbyte.com/platform/2.0/contributing-to-airbyte/developing-locally#connector-contributions)] A forum answer also confirms you can build a modified connector locally (e.g., via Gradle) and then add it as a custom connector in the UI, even if the image is not published anywhere. [[Forum post](https://discuss.airbyte.io/t/1812)] --- ## 2. “Clone” as in re‑use / reconfigure a MongoDB source If by “clone” you mean set up another MongoDB V2 source with similar settings: - Create a new MongoDB V2 source in the Airbyte UI and configure it with the appropriate connection string, databases, and credentials. [[MongoDB quick start](https://docs.airbyte.com/integrations/sources/mongodb-v2#quick-start); [MongoDB config params](https://docs.airbyte.com/integrations/sources/mongodb-v2#configuration-parameters)] - The docs do not describe a one-click “duplicate source” feature, so any cloning of configuration would be manual (re-entering the same parameters) or done via external tooling (e.g., Terraform), which is not detailed specifically for MongoDB in these sources. If you clarify which of these you meant (code-level clone vs. duplicating a configured source), I can narrow the steps further based only on the docs.