This release is a pre-release and may not be stable for production use.
Airbyte Python CDK and Low-Code CDK
Airbyte Python CDK is a framework for building Airbyte API Source Connectors. It provides a set of classes and helpers that make it easy to build a connector against an HTTP API (REST, GraphQL, etc), or a generic Python source connector.
Building Connectors with the CDK
If you're looking to build a connector, we highly recommend that you first
start with the Connector Builder.
It should be enough for 90% connectors out there. For more flexible and complex connectors, use the
low-code CDK and SourceDeclarativeManifest.
For more information on building connectors, please see the Connector Development guide on docs.airbyte.com.
Python CDK Overview
Airbyte CDK code is within airbyte_cdk directory. Here's a high level overview of what's inside:
airbyte_cdk/connector_builder. Internal wrapper that helps the Connector Builder platform run a declarative manifest (low-code connector). You should not use this code directly. If you need to run aSourceDeclarativeManifest, take a look atsource-declarative-manifestconnector implementation instead.airbyte_cdk/cli/source_declarative_manifest. This module defines thesource-declarative-manifest(aka "SDM") connector execution logic and associated CLI.airbyte_cdk/destinations. Basic Destination connector support! If you're building a Destination connector in Python, try that. Some of our vector DB destinations likedestination-pineconeare using that code.airbyte_cdk/modelsexposeairbyte_protocol.modelsas a part ofairbyte_cdkpackage.airbyte_cdk/sources/concurrent_sourceis the Concurrent CDK implementation. It supports reading data from streams concurrently per slice / partition, useful for connectors with high throughput and high number of records.airbyte_cdk/sources/declarativeis the low-code CDK. It works on top of Airbyte Python CDK, but provides a declarative manifest language to define streams, operations, etc. This makes it easier to build connectors without writing Python code.airbyte_cdk/sources/file_basedis the CDK for file-based sources. Examples include S3, Azure, GCS, etc.
Contributing
For instructions on how to contribute, please see our Contributing Guide.
Release Management
Please see the Release Management guide for information on how to perform releases and pre-releases.
1 maintainer
Metadata
1 maintainer
Release files for airbyte-cdk 6.38.3.dev4101
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| airbyte_cdk-6.38.3.dev4101.tar.gz | 426.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| airbyte_cdk-6.38.3.dev4101-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / airbyte_cdk-6.38.3.dev4101.tar.gz
| Download URL | airbyte_cdk-6.38.3.dev4101.tar.gz |
|---|---|
| Size | 426.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8bd8e18cfdb687043fed1ef877791a75f4457522fa320b5a2bb321389b4b2aff
|
|
BLAKE2b-256 checksum How to use checksums |
77c36724ea9cd3b623c5342831a9f91724cde432cc0c21616af914254d42ad35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 10, 2025.
Transparency logRelease files / airbyte_cdk-6.38.3.dev4101-py3-none-any.whl
| Download URL | airbyte_cdk-6.38.3.dev4101-py3-none-any.whl |
|---|---|
| Size | 607.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04d98ee2954342920cb3afeeb58208ad24f62a716d7d0b2333acb2e7808ff4f1
|
|
BLAKE2b-256 checksum How to use checksums |
e32b2f14310b1e7cb82814cfaea9df6e1d2c76f0f5cc1d26a1b905b9c63fe759
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 10, 2025.
Transparency log
