Skip to main content

Data Engineering Toolkit compiler

The det CLI turns the controlled V4.1.1 official-ODCS Excel superset into canonical ODCS, DET execution metadata, and a readable dbt project. It includes safe questionnaire-based workbook creation, ODCS/DDL/dbt-to-Excel import and merge-safe synchronization, source-schema import, cross-sheet semantic/type validation, atomic post-sync generation, Data Contract synchronization, SQLFluff, and the isolated det prove acceptance flow. Data Contract CLI, dbt Core, DuckDB, and SQLFluff are default dependencies.

V4.1.1 makes the visible official Quality sheet authoritative, preserves advanced per-rule ODCS values, supports eight production warehouse providers, and adds mandatory 85.01% Python statement coverage. The generated dbt package has 98.53% DuckDB-scoped macro implementation coverage plus 100% public-API direct execution coverage and supports dbt Core plus Fusion-compatible projects. External resources are isolated behind brokers; reusable services interpret workbooks and input formats; independent components validate with stable diagnostic codes; and one emitter owns each artifact family. The CLI remains a thin exposer over ToolkitApplication.

Install

python -m pip install dbt-data-engineering-toolkit-compiler==4.1.1

The default installation includes Data Contract CLI, dbt Core, dbt-duckdb, DuckDB, and SQLFluff. Install one additional warehouse adapter per deployment environment, for example:

python -m pip install "dbt-data-engineering-toolkit-compiler[snowflake]"

Supported extras are athena, bigquery, clickhouse, databricks, duckdb, postgres, redshift, snowflake, and spark.

Workflow

Use this sequence to move from workbook design to validated, testable dbt delivery.

Step Business action Outcome Command
1 Run the guided, safe workbook builder Product basics; no demo rows by default det workbook build PRODUCT.xlsx
2 Import or define target structures ODCS model and property rows det workbook import ...
3 Register/import upstream sources Checked source fields and types det source import ...
4 Define model inputs, mappings, and joins Context-aware fields and executable cardinality checks det workbook refresh PRODUCT.xlsx
5 Add contract rules on Quality; runtime handling on Operational Validation ODCS tests, warnings, and quarantine with one clear authority Use workbook sheets (no CLI command)
6 Validate the workbook Actionable cross-sheet diagnostics det validate PRODUCT.xlsx
7 Preview generated changes No files changed det generate PRODUCT.xlsx --project-dir dbt_product --dry-run --prune
8 Export package environment variables, then generate, sync, and lint dbt packages resolve from your published Git URL and pinned revision export DBT_DATA_ENGINEERING_TOOLKIT_GIT_URL=https://github.com/systemizing-solutions/dbt_data_engineering_toolkit.git; det generate ...; dbt deps; det check ...
9 Run isolated acceptance Contract, dbt tests, evaluator det prove PRODUCT.xlsx --project-dir dbt_product
10 Merge later schema changes Mappings and rules preserved det workbook sync ...
Demo Opt in only when explicitly wanted Multi-source customer training rows det workbook build demo.xlsx --sample-customer-data

Before running dbt deps, set the package source URL used by generated packages.yml:

export DBT_DATA_ENGINEERING_TOOLKIT_GIT_URL=https://github.com/systemizing-solutions/dbt_data_engineering_toolkit.git

If you need a custom variable name, set Toolkit Git Env on the DET Build sheet before det generate, then export that variable name in your shell.

Quick start

det workbook build data_product.xlsx --no-input
det validate data_product.xlsx

The default is blank and does not add demonstration sample data. Use --sample-customer-data only when you explicitly want a demonstration workbook.

Continue with det --help and det workbook --help. The source repository root README contains the complete workbook-to-ODCS-to-dbt walkthrough, architecture, compatibility matrix, testing definitions, and deployment guide.

Metadata

Release files for dbt-data-engineering-toolkit-compiler 4.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dbt-data-engineering-toolkit-compiler 4.1.1
File Size Uploaded
dbt_data_engineering_toolkit_compiler-4.1.1.tar.gz 268.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dbt-data-engineering-toolkit-compiler 4.1.1
File Interpreter ABI Platform
dbt_data_engineering_toolkit_compiler-4.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 558.9 kB

Release files / dbt_data_engineering_toolkit_compiler-4.1.1.tar.gz

Download URL dbt_data_engineering_toolkit_compiler-4.1.1.tar.gz
Size 268.6 kB
Tags Source
SHA-256 checksum
How to use checksums
e108d3f688aa890582ea8443e6930aca2519700f0ef94fa9f3e836b0835bd135
BLAKE2b-256 checksum
How to use checksums
de40137721514fae42151ff7c2c3d82d37bf4a7d27e2c5c54ee68aa2fd9d6236
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 10, 2026.

Transparency log

Release files / dbt_data_engineering_toolkit_compiler-4.1.1-py3-none-any.whl

Download URL dbt_data_engineering_toolkit_compiler-4.1.1-py3-none-any.whl
Size 290.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
37451ae72488093814b90859f27cc9d018ac8b735477c8df40d5bac346d7998f
BLAKE2b-256 checksum
How to use checksums
4f628dba4305e2c663b5f5d72aed87ab81a13cef71897fc59079419b7e9521f9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 10, 2026.

Transparency log

Release history Release notifications | RSS feed

6.0.0

2 release files

5.0.1

2 release files

This release

4.1.1 This release

2 release files

4.0.3

2 release files

4.0.2

2 release files

4.0.1

2 release files

4.0.0

2 release files

3.2.0

2 release files

3.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page