chore: cleanup remaining airbyte-ci references in docs, poe-tasks, devcontainer, and misc files (#75953)

aaronsteers · devin-ai-integration[bot] · github-actions[bot] · web-flow · commit 296257733835 · 2026-03-31T17:36:18.000-07:00
Co-authored-by: Devin AI &lt;158243242+devin-ai-integration[bot]@users.noreply.github.com&gt;
Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;
diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
@@ -10,7 +10,6 @@
       "jdkDistro": "open",
       "gradleVersion": "7.5.1"
     },
-    // Python needed for `airbyte-ci` CLI
     "ghcr.io/devcontainers/features/python:1": {
       "installGradle": true,
       "version": "3.10",
@@ -57,8 +56,7 @@
   },
   // Mark the root directory as 'safe' for git.
   "initializeCommand": "git config --add safe.directory /workspaces/airbyte",
-  // Install Gradle, `airbyte-ci` CLI, and Dagger (installed via airbyte-ci --help)
-  "postCreateCommand": "make tools.airbyte-ci-dev.install",
+  "postCreateCommand": "uv tool install airbyte-cdk",
   "containerEnv": {
     // Deterministic Poetry virtual env location: `./.venv`
     "POETRY_VIRTUALENVS_IN_PROJECT": "true"
diff --git a/.devcontainer/java-connectors-generic/devcontainer.json b/.devcontainer/java-connectors-generic/devcontainer.json
@@ -11,7 +11,6 @@
       "jdkDistro": "open",
       "gradleVersion": "7.5.1"
     },
-    // Python needed for `airbyte-ci` CLI
     "ghcr.io/devcontainers/features/python:1": {
       "installGradle": true,
       "version": "3.10",
@@ -42,8 +41,8 @@
   // Mark the root directory as 'safe' for git.
   "initializeCommand": "git config --add safe.directory /workspaces/airbyte",
 
-  // Install `airbyte-ci` and Gradle
-  "postCreateCommand": "make tools.airbyte-ci-dev.install && ./gradlew --version",
+  // Install dependencies and warm up Gradle
+  "postCreateCommand": "uv tool install airbyte-cdk && ./gradlew --version",
 
   "containerEnv": {
     // Deterministic Poetry virtual env location: `./.venv`
diff --git a/.devcontainer/python-connectors-generic/devcontainer.json b/.devcontainer/python-connectors-generic/devcontainer.json
@@ -49,8 +49,8 @@
   // Mark the root directory as 'safe' for git.
   "initializeCommand": "git config --add safe.directory /workspaces/airbyte",
 
-  // Setup airbyte-ci on the container:
-  "postCreateCommand": "make tools.airbyte-ci-dev.install",
+  // Install the Airbyte CDK:
+  "postCreateCommand": "uv tool install airbyte-cdk",
 
   "containerEnv": {
     // Deterministic Poetry virtual env location: `./.venv`
diff --git a/airbyte-integrations/connectors/destination-mysql/src/test-integration/kotlin/io/airbyte/integrations/destination/mysql/typing_deduping/AbstractMysqlTypingDedupingTest.kt b/airbyte-integrations/connectors/destination-mysql/src/test-integration/kotlin/io/airbyte/integrations/destination/mysql/typing_deduping/AbstractMysqlTypingDedupingTest.kt
@@ -94,8 +94,8 @@ abstract class AbstractMysqlTypingDedupingTest : JdbcTypingDedupingTest(SQLDiale
         private lateinit var containerizedConfig: ObjectNode
         /**
          * The config with host/port accessible from the host's network. (technically, this is still
-         * within the airbyte-ci container, but `containerizedConfig` is intended for containers in
-         * the docker-in-docker matryoshka doll)
+         * within the CI container, but `containerizedConfig` is intended for containers in the
+         * docker-in-docker matryoshka doll)
          */
         private lateinit var bareMetalConfig: ObjectNode
 
diff --git a/airbyte-integrations/connectors/destination-mysql/src/testFixtures/kotlin/io/airbyte/integrations/destination/mysql/MysqlTestDatabase.kt b/airbyte-integrations/connectors/destination-mysql/src/testFixtures/kotlin/io/airbyte/integrations/destination/mysql/MysqlTestDatabase.kt
@@ -31,7 +31,7 @@ class MysqlTestDatabase(container: MySQLContainer<*>) :
 
     override fun inContainerBootstrapCmd(): Stream<Stream<String>> {
         // Besides setting up user and privileges, we also need to create a soft link otherwise
-        // airbyte-ci on github runner would not be able to connect to DB, because the sock file
+        // CI on github runner would not be able to connect to DB, because the sock file
         // does not
         // exist.
         return Stream.of(
diff --git a/airbyte-integrations/connectors/source-microsoft-lists/metadata.yaml b/airbyte-integrations/connectors/source-microsoft-lists/metadata.yaml
@@ -27,7 +27,7 @@ data:
   releaseStage: alpha
   supportLevel: community
   connectorTestSuitesOptions:
-    # no-op for now but will get enabled when the capability is added to airbyte-ci
+    # no-op for now but will get enabled when the capability is added to CI
     - suite: integrationTests
       testSecrets:
         - name: SECRET_SOURCE-MICROSOFT-LISTS_CREDS
diff --git a/buildSrc/src/main/groovy/airbyte-bulk-connector.gradle b/buildSrc/src/main/groovy/airbyte-bulk-connector.gradle
@@ -203,8 +203,7 @@ class AirbyteBulkConnectorPlugin implements Plugin<Project> {
                 outputs.upToDateWhen { false }
             }
 
-            // For historical reasons (i.e. airbyte-ci), this task is called integrationTestJava.
-            // airbyte-ci only wants to run a task with exactly that name.
+            // For historical reasons, this task is called integrationTestJava.
             // There's intentionally no equivalent to run integrationTestNonDocker + integrationTestLegacy.
             // It's an actual Test task (rather than just depending on two sub-tasks integrationTestDocker + integrationTestLegacy)
             // so that gradle args (e.g. `--tests`) work as expected.
diff --git a/docs/community/contributing-to-airbyte/resources/qa-checks.md b/docs/community/contributing-to-airbyte/resources/qa-checks.md
@@ -1,9 +1,7 @@
 # Airbyte connectors QA checks
 
 <!--
-THIS FILE IS GENERATED BY THE CONNECTORS-QA CLI. DO NOT EDIT THIS FILE MANUALLY. 
-IF YOU NEED TO EDIT IT, EDIT THE TEMPLATE: https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/templates/qa_checks.md.j2
-AND REGENERATE THE DOCS BY RUNNING `connectors-qa generate-documentation docs/community/contributing-to-airbyte/resources/qa-checks.md` FROM THE AIRBYTE REPO ROOT
+THIS FILE IS GENERATED BY THE CONNECTORS-QA CLI. DO NOT EDIT THIS FILE MANUALLY.
 -->
 
 This document is listing all the static-analysis checks that are performed on the Airbyte connectors.
@@ -54,7 +52,7 @@ _Applies to connector with any support level_
 _Applies to connector with 300 internal support level_
 _Applies to connector with any Airbyte usage level_
 
-The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the standard template.
 
 This check expects the following order of headers in the documentation:
 
@@ -143,7 +141,7 @@ _Applies to connector with any support level_
 _Applies to connector with 300 internal support level_
 _Applies to connector with any Airbyte usage level_
 
-The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the standard template.
 
 Check verifies that CONNECTOR_NAME_FROM_METADATA header section content follows standard template:
 
@@ -166,7 +164,7 @@ _Applies to connector with any support level_
 _Applies to connector with 300 internal support level_
 _Applies to connector with any Airbyte usage level_
 
-The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the standard template.
 
 Check verifies that For Airbyte Cloud: header section content follows standard template:
 
@@ -187,7 +185,7 @@ _Applies to connector with any support level_
 _Applies to connector with 300 internal support level_
 _Applies to connector with any Airbyte usage level_
 
-The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the standard template.
 
 Check verifies that For Airbyte Open Source: header section content follows standard template:
 
@@ -205,7 +203,7 @@ _Applies to connector with any support level_
 _Applies to connector with 300 internal support level_
 _Applies to connector with any Airbyte usage level_
 
-The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the standard template.
 
 Check verifies that Supported sync modes header section content follows standard template:
 
@@ -224,7 +222,7 @@ _Applies to connector with any support level_
 _Applies to connector with 300 internal support level_
 _Applies to connector with any Airbyte usage level_
 
-The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the standard template.
 
 Check verifies that Tutorials header section content follows standard template:
 
@@ -243,7 +241,7 @@ _Applies to connector with any support level_
 _Applies to connector with 300 internal support level_
 _Applies to connector with any Airbyte usage level_
 
-The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the standard template.
 
 Check verifies that Changelog header section content follows standard template:
 
diff --git a/docs/platform/connector-development/cdk-python/migration-to-base-image.md b/docs/platform/connector-development/cdk-python/migration-to-base-image.md
@@ -7,7 +7,7 @@ N.B: This guide currently only applies to Python CDK connectors.
 
 ## Prerequisite
 
-[Install the airbyte-ci tool](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md#L1)
+Ensure you have the [Airbyte CDK](https://pypi.org/project/airbyte-cdk/) installed.
 
 ## Definition of a successful migration
 
@@ -36,7 +36,7 @@ In other word, using the image digest (sha256), we have the guarantee that a bui
 
 ### What if my connector needs specific system dependencies?
 
-Declaring the base image in the metadata.yaml file makes the Dockerfile obselete and the connector will be built using our internal build process declared [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/pipelines/airbyte_ci/connectors/build_image/steps/python_connectors.py#L55).
+Declaring the base image in the metadata.yaml file makes the Dockerfile obsolete and the connector will be built using our internal build process.
 If your connector has specific system dependencies, or has to set environment variables, we have a pre/post build hook framework for that.
 
 You can customize our build process by adding a `build_customization.py` module to your connector.
@@ -63,16 +63,6 @@ async def post_connector_install(connector_container: Container) -> Container:
     return await connector_container.with_env_variable("MY_POST_BUILD_ENV_VAR", "my_post_build_env_var_value")
 ```
 
-### Listing migrated / non migrated connectors:
+### Listing migrated / non migrated connectors
 
-To list all migrated certified connectors you can ran:
-
-```bash
-airbyte-ci connectors --support-level=certified --metadata-query="data.connectorBuildOptions.baseImage is not None" list
-```
-
-To list all non migrated certified connectors you can ran:
-
-```bash
-airbyte-ci connectors --metadata-query="data.supportLevel == 'certified' and 'connectorBuildOptions' not in data.keys()" list
-```
+You can check connector metadata files to see which connectors have migrated to the base image by looking for the `data.connectorBuildOptions.baseImage` key in their `metadata.yaml` files.
diff --git a/docs/platform/connector-development/connector-metadata-file.md b/docs/platform/connector-development/connector-metadata-file.md
@@ -221,9 +221,9 @@ To enable a test suite, add the suite name to the `connectorTestSuitesOptions` l
             alias: airbyte-connector-testing-secret-store
 ```
 
-#####  Default paths and conventions
- 
-The [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) tool will automatically locate specific test types based on established conventions and will automatically store secret files (when needed) in the established secrets directory - which should be already excluded from accidental git commits.
+##### Default paths and conventions
+
+The CI pipeline will automatically locate specific test types based on established conventions and will automatically store secret files (when needed) in the established secrets directory - which should be already excluded from accidental git commits.
 
 **Python connectors**
 Tests are discovered by Pytest and are expected to be located in:
@@ -232,7 +232,7 @@ Tests are discovered by Pytest and are expected to be located in:
 
 **Java connectors**
 No specific directory is determined. Which test will run is determined by the Gradle configuration of the connector.
-`airbyt-ci` runs the `test` Gradle task for the `unitTests` suite and the `integrationTest` Gradle task for the `integrationTests` suite.
+CI runs the `test` Gradle task for the `unitTests` suite and the `integrationTest` Gradle task for the `integrationTests` suite.
 
 **Acceptance tests**
 
diff --git a/docs/platform/connector-development/submit-new-connector.md b/docs/platform/connector-development/submit-new-connector.md
@@ -45,7 +45,7 @@ This will enable our team to make sure your contribution does not overlap with e
 
 ### Open a pull request
 
-1. Make sure your connector passes `airbyte-ci connectors test` tests. [Here's a guide on how to run them](../connector-development/testing-connectors/README.md).
+1. Make sure your connector passes the test suite. [Here's a guide on how to run them](../connector-development/testing-connectors/README.md).
 2. Make sure you include the README, documentation, and an icon for your connector. Without them, one of the CI checks will fail.
 3. Follow the [pull request convention](/community/contributing-to-airbyte/resources/pull-requests-handbook#pull-request-title-convention)
 4. Wait for a review from a community maintainer or our team. We generally look for the following criteria:
diff --git a/docs/platform/connector-development/testing-connectors/README.md b/docs/platform/connector-development/testing-connectors/README.md
@@ -8,22 +8,15 @@ Multiple tests suites compose the Airbyte connector testing pyramid
 - Unit Tests: Connector-specific tests written by the connector developer which don’t require access to the source/destination.
 - Integration Tests: Connector-specific tests written by the connector developer which _may_ require access to the source/destination.
 - [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference/): Connector-agnostic tests that verify that a connector adheres to the [Airbyte protocol](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol). Credentials to a source/destination sandbox account are **required**.
-- [Regression Tests](https://github.com/airbytehq/airbyte/tree/master/airbyte-ci/connectors/live-tests): Connector-agnostic tests that verify that the behavior of a connector hasn’t changed unexpectedly between connector versions. A sandbox cloud connection is required. Currently only available for API source connectors.
+- Regression Tests (deprecated): Connector-agnostic tests that verified the behavior of a connector between versions. Previously available for API source connectors.
 
 
 ## 🤖 CI
 
-If you want to run the global test suite, exactly like what is run in CI, you should install [`airbyte-ci` CLI](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) and use the following command:
-
-```bash
-airbyte-ci connectors --name=<connector_name> test
-```
-
 CI will run all the tests that are available for a connector. This can include all of the tests listed above, if we have the appropriate credentials. At a minimum, it will include the Connector QA checks and any tests that exist in a connector's `unit_tests` and `integration_tests` directories.
 To run Connector Acceptance tests locally, you must provide connector configuration as a `config.json` file in a `.secrets` folder in the connector code directory.
-Regression tests may only be run locally with authorization to our cloud resources.
 
-Our CI infrastructure runs the connector tests with [`airbyte-ci` CLI](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md). Connectors tests are automatically and remotely triggered on your branch according to the changes made in your branch.
+Connector tests are automatically and remotely triggered on your branch according to the changes made in your branch.
 **Passing tests are required to merge a connector pull request.**
 
 ## Connector specific tests
diff --git a/docs/platform/connector-development/testing-connectors/connector-acceptance-tests-reference.md b/docs/platform/connector-development/testing-connectors/connector-acceptance-tests-reference.md
@@ -32,19 +32,17 @@ _Note: Not all types of tests work for all connectors, only configure the ones t
 
 Build your connector image if needed.
 
-**Option A (Preferred): Building the docker image with `airbyte-ci`**
+**Option A (Preferred): Building the docker image with the Airbyte CDK**
 
 This is the preferred method for building and testing connectors.
 
-If you want to open source your connector we encourage you to use our [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) tool to build your connector.
-It will not use a Dockerfile but will build the connector image from our [base image](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/base_images/README.md) and use our internal build logic to build an image from your Python connector code.
+The build process will not use a Dockerfile but will build the connector image from our base image and use our internal build logic to build an image from your Python connector code.
 
-Running `airbyte-ci connectors --name source-<source-name> build` will build your connector image.
-Once the command is done, you will find your connector image in your local docker host: `airbyte/source-<source-name>:dev`.
+Once the build is done, you will find your connector image in your local docker host: `airbyte/source-<source-name>:dev`.
 
 **Option B: Building the docker image with a Dockerfile**
 
-If you don't want to rely on `airbyte-ci` to build your connector, you can build the docker image using your own Dockerfile. This method is not preferred, and is not supported for certified connectors.
+You can also build the docker image using your own Dockerfile. This method is not preferred, and is not supported for certified connectors.
 
 Create a `Dockerfile` in the root of your connector directory. The `Dockerfile` should look something like this:
 
@@ -70,30 +68,11 @@ docker build . -t airbyte/source-example-python:dev
 
 And test via one of the two following Options
 
-### Option 1 (Preferred): Run against the Airbyte CI test suite
+### Running acceptance tests
 
-Learn how to use and install [`airbyte-ci` here](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md). Once installed, `airbyte-ci connectors test` command will run unit, integration, and acceptance tests against your connector. Pass `--name <your_connector_name>` to test just one connector.
+Connector acceptance tests are run automatically in CI when you open a pull request. The CI pipeline will run unit, integration, and acceptance tests against your connector.
 
-```bash
-airbyte-ci connectors --name=<name-of-your-connector></name-of-your-connector> test
-```
-
-### Option 2 (Debugging): Run against the acceptance tests on your branch
-
-This will run the acceptance test suite directly with pytest. Allowing you to set breakpoints and debug your connector locally.
-
-The only pre-requisite is that you have [Poetry](https://python-poetry.org/docs/#installation) installed.
-
-Afterwards you do the following from the root of the `airbyte` repo:
-
-```bash
-cd airbyte-integrations/bases/connector-acceptance-test/
-poetry install
-poetry run pytest -p connector_acceptance_test.plugin --acceptance-test-config=../../connectors/<your-connector> --pdb
-```
-
-See other useful pytest options [here](https://docs.pytest.org/en/stable/usage.html)
-See a more comprehensive guide in our README [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/bases/connector-acceptance-test/README.md)
+See useful pytest options [here](https://docs.pytest.org/en/stable/usage.html).
 
 ## Dynamically managing inputs & resources used in standard tests
 
diff --git a/poe-tasks/gradle-connector-tasks.toml b/poe-tasks/gradle-connector-tasks.toml
@@ -84,6 +84,4 @@ help = "Get the base image of the connector from its metadata.yaml file."
 cmd = """yq eval '.data.dockerImageTag' ${POE_PWD}/metadata.yaml"""
 help = "Get the version of the connector from its metadata.yaml file."
 
-[tasks.run-cat-tests]
-shell = "airbyte-ci connectors --name=`poe -qq get-connector-name` test --only-step=acceptance"
-help = "Run the legacy Airbyte-CI acceptance tests (CAT tests)."
+# [tasks.run-cat-tests] - Removed: airbyte-ci CLI and CAT tests have been deprecated.
diff --git a/poe-tasks/manifest-only-connector-tasks.toml b/poe-tasks/manifest-only-connector-tasks.toml
diff --git a/poe-tasks/poetry-connector-tasks.toml b/poe-tasks/poetry-connector-tasks.toml
diff --git a/poe-tasks/publish-python-registry.sh b/poe-tasks/publish-python-registry.sh

Original file line number	Diff line number	Diff line change
`@@ -203,8 +203,7 @@ class AirbyteBulkConnectorPlugin implements Plugin<Project> {`
`203`	`203`	`outputs.upToDateWhen { false }`
`204`	`204`	`}`
`205`	`205`
`206`		`- // For historical reasons (i.e. airbyte-ci), this task is called integrationTestJava.`
`207`		`- // airbyte-ci only wants to run a task with exactly that name.`
	`206`	`+ // For historical reasons, this task is called integrationTestJava.`
`208`	`207`	`// There's intentionally no equivalent to run integrationTestNonDocker + integrationTestLegacy.`
`209`	`208`	`// It's an actual Test task (rather than just depending on two sub-tasks integrationTestDocker + integrationTestLegacy)`
`210`	`209`	// so that gradle args (e.g. `--tests`) work as expected.