datacontract-cli 0.12.2__tar.gz → 0.12.3__tar.gz

{datacontract_cli-0.12.2/datacontract_cli.egg-info → datacontract_cli-0.12.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: datacontract-cli
-Version: 0.12.2
+Version: 0.12.3
 Summary: The datacontract CLI is an open source command-line tool for working with Data Contracts. It uses data contract YAML files to lint the data contract, connect to data sources and execute schema and quality tests, detect breaking changes, and export to different formats. The tool is written in Python. It can be used as a standalone CLI tool, in a CI/CD pipeline, or directly as a Python library.
 Author-email: Jochen Christ <jochen.christ@innoq.com>, Stefan Negele <stefan.negele@innoq.com>, Simon Harrer <simon.harrer@innoq.com>
 License-Expression: MIT
@@ -14,7 +14,7 @@ License-File: LICENSE
 Requires-Dist: typer<0.26,>=0.18.0
 Requires-Dist: pydantic<2.14.0,>=2.8.2
 Requires-Dist: pyyaml~=6.0.1
-Requires-Dist: requests<2.34,>=2.31
+Requires-Dist: requests<2.35,>=2.31
 Requires-Dist: fastjsonschema<2.22.0,>=2.19.1
 Requires-Dist: jsonschema<5.0.0,>=4.23.0
 Requires-Dist: pytz>=2024.1
@@ -41,7 +41,7 @@ Provides-Extra: databricks
 Requires-Dist: soda-core-spark-df<3.6.0,>=3.3.20; extra == "databricks"
 Requires-Dist: soda-core-spark[databricks]<3.6.0,>=3.3.20; extra == "databricks"
 Requires-Dist: databricks-sql-connector<4.3.0,>=3.7.0; extra == "databricks"
-Requires-Dist: databricks-sdk<0.106.0; extra == "databricks"
+Requires-Dist: databricks-sdk<0.109.0; extra == "databricks"
 Requires-Dist: pyspark<5.0.0,>=3.5.0; extra == "databricks"
 Provides-Extra: iceberg
 Requires-Dist: pyiceberg==0.11.1; extra == "iceberg"
@@ -54,11 +54,13 @@ Requires-Dist: soda-core-mysql<3.6.0,>=3.3.20; extra == "mysql"
 Requires-Dist: mysql-connector-python<9.7.0,>=8.0.30; extra == "mysql"
 Provides-Extra: postgres
 Requires-Dist: soda-core-postgres<3.6.0,>=3.3.20; extra == "postgres"
+Provides-Extra: redshift
+Requires-Dist: soda-core-redshift<3.6.0,>=3.3.20; extra == "redshift"
 Provides-Extra: s3
 Requires-Dist: s3fs<2027.0.0,>=2025.2.0; extra == "s3"
-Requires-Dist: aiobotocore<3.6.0,>=2.17.0; extra == "s3"
+Requires-Dist: aiobotocore<3.8.0,>=2.17.0; extra == "s3"
 Provides-Extra: snowflake
-Requires-Dist: snowflake-connector-python[pandas]<4.5,>=3.6; extra == "snowflake"
+Requires-Dist: snowflake-connector-python[pandas]<4.6,>=3.6; extra == "snowflake"
 Requires-Dist: soda-core-snowflake<3.6.0,>=3.3.20; extra == "snowflake"
 Provides-Extra: sqlserver
 Requires-Dist: soda-core-sqlserver<3.6.0,>=3.3.20; extra == "sqlserver"
@@ -81,19 +83,19 @@ Provides-Extra: rdf
 Requires-Dist: rdflib==7.6.0; extra == "rdf"
 Provides-Extra: api
 Requires-Dist: fastapi==0.136.1; extra == "api"
-Requires-Dist: uvicorn==0.44.0; extra == "api"
+Requires-Dist: uvicorn<0.47.0,>=0.44.0; extra == "api"
 Provides-Extra: protobuf
-Requires-Dist: protobuf<7.0,>=3.20; extra == "protobuf"
+Requires-Dist: protobuf<8.0,>=3.20; extra == "protobuf"
 Provides-Extra: all
-Requires-Dist: datacontract-cli[api,athena,bigquery,csv,databricks,dbml,duckdb,excel,iceberg,impala,kafka,mysql,oracle,parquet,postgres,protobuf,rdf,s3,snowflake,sqlserver,trino]; extra == "all"
+Requires-Dist: datacontract-cli[api,athena,bigquery,csv,databricks,dbml,duckdb,excel,iceberg,impala,kafka,mysql,oracle,parquet,postgres,protobuf,rdf,redshift,s3,snowflake,sqlserver,trino]; extra == "all"
 Provides-Extra: dev
 Requires-Dist: datacontract-cli[all]; extra == "dev"
 Requires-Dist: httpx==0.28.1; extra == "dev"
 Requires-Dist: kafka-python; extra == "dev"
 Requires-Dist: minio==7.2.20; extra == "dev"
-Requires-Dist: moto==5.1.22; extra == "dev"
+Requires-Dist: moto==5.2.1; extra == "dev"
 Requires-Dist: pandas>=2.1.0; extra == "dev"
-Requires-Dist: pre-commit<4.6.0,>=3.7.1; extra == "dev"
+Requires-Dist: pre-commit<4.7.0,>=3.7.1; extra == "dev"
 Requires-Dist: pytest; extra == "dev"
 Requires-Dist: pytest-xdist; extra == "dev"
 Requires-Dist: pymssql==2.3.13; extra == "dev"
@@ -230,6 +232,9 @@ $ datacontract changelog v1.odcs.yaml v2.odcs.yaml
 # execute schema and quality checks (define credentials as environment variables)
 $ datacontract test odcs.yaml
 
+# generate dbt tests from a contract into your dbt project and run `dbt test`
+$ datacontract dbt sync orders.odcs.yaml --project-dir ./warehouse
+
 # export data contract as html (other formats: avro, dbt-models, dbt-sources, dbt-staging-sql, jsonschema, odcs, rdf, sql, sodacl, terraform, ...)
 $ datacontract export html datacontract.yaml --output odcs.html
 
@@ -359,6 +364,7 @@ A list of available extras:
 | PostgreSQL Integration  | `pip install datacontract-cli[postgres]`   |
 | protobuf                | `pip install datacontract-cli[protobuf]`   |
 | RDF                     | `pip install datacontract-cli[rdf]`        |
+| Amazon Redshift         | `pip install datacontract-cli[redshift]`   |
 | S3 Integration          | `pip install datacontract-cli[s3]`         |
 | Snowflake Integration   | `pip install datacontract-cli[snowflake]`  |
 | Microsoft SQL Server    | `pip install datacontract-cli[sqlserver]`  |
@@ -374,6 +380,7 @@ Commands
 - [lint](#lint)
 - [changelog](#changelog)
 - [test](#test)
+- [dbt](#dbt-sync)
 - [ci](#ci)
 - [export](#export)
 - [import](#import)
@@ -444,13 +451,19 @@ Commands
  Show a changelog between two data contracts.                                                       
                                                                                                     
 ╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────╮
-│ *    v1      TEXT  The location (path) of the source (before) data contract YAML. [required]     │
-│ *    v2      TEXT  The location (path) of the target (after) data contract YAML. [required]      │
+│ *    v1      TEXT  The location (url or path) of the source (before) data contract YAML.         │
+│                    [required]                                                                    │
+│ *    v2      TEXT  The location (url or path) of the target (after) data contract YAML.          │
+│                    [required]                                                                    │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
 ╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
 │ --debug    --no-debug      Enable debug logging                                                  │
 │ --help                     Show this message and exit.                                           │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+                                                                                                    
+ Example: datacontract changelog datacontract-v1.yaml datacontract-v2.yaml                          
+                                                                                                    
+
 ```
 
 ```bash
@@ -1044,6 +1057,52 @@ models:
 
 </details>
 
+<details markdown="1">
+<summary><strong>Amazon Redshift</strong></summary>
+
+Data Contract CLI can test data in Amazon Redshift (both provisioned clusters and Redshift Serverless).
+
+##### Example
+
+datacontract.yaml
+```yaml
+servers:
+  redshift:
+    type: redshift
+    host: my-workgroup.123456789012.us-east-1.redshift-serverless.amazonaws.com
+    port: 5439
+    database: dev
+    schema: analytics
+models:
+  my_table_1: # corresponds to a table
+    type: table
+    fields:
+      my_column_1: # corresponds to a column
+        type: varchar
+```
+
+##### Environment Variables
+All [parameters supported by Soda](https://docs.soda.io/soda/connect-redshift.html), uppercased and prepended by `DATACONTRACT_REDSHIFT_` prefix.
+For example:
+
+| Soda parameter      | Environment Variable                      | Details             |
+|---------------------|-------------------------------------------|---------------------|
+| `username`          | `DATACONTRACT_REDSHIFT_USERNAME`          |                     |
+| `password`          | `DATACONTRACT_REDSHIFT_PASSWORD`          | leave unset for IAM |
+| `region`            | `DATACONTRACT_REDSHIFT_REGION`            | for IAM             |
+| `access_key_id`     | `DATACONTRACT_REDSHIFT_ACCESS_KEY_ID`     | for IAM             |
+| `secret_access_key` | `DATACONTRACT_REDSHIFT_SECRET_ACCESS_KEY` | for IAM             |
+| `role_arn`          | `DATACONTRACT_REDSHIFT_ROLE_ARN`          | for IAM             |
+
+IAM credentials can be supplied in two ways:
+
+1. **AWS_PROFILE** — set `AWS_PROFILE` in your shell to a profile defined in `~/.aws/credentials` and `DATACONTRACT_REDSHIFT_REGION`.
+2. **Explicit keys** — set `DATACONTRACT_REDSHIFT_REGION`, `..._ACCESS_KEY_ID`, `..._SECRET_ACCESS_KEY`, and `..._SESSION_TOKEN` for temporary credentials, or `..._ROLE_ARN` to assume a role.
+
+>IAM authentication is supported only for **provisioned** Redshift clusters.
+
+</details>
+
 <details markdown="1">
 <summary><strong>MySQL</strong></summary>
 
@@ -1223,6 +1282,84 @@ models:
 
 </details>
 
+### dbt sync
+> The `dbt sync` command is still work in progress and will receive further functionality and documentation soon.
+```
+                                                                                                    
+ Usage: datacontract dbt sync [OPTIONS] [CONTRACT]                                                  
+                                                                                                    
+ Generate dbt tests from an ODCS contract and run them.                                             
+                                                                                                    
+ Within the specified dbt project, this command wipes `<model-paths>/datacontract_cli/` and         
+ `<test-paths>/datacontract_cli/`, regenerates them from the contract, then runs `dbt test`.        
+                                                                                                    
+╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────╮
+│   contract      [CONTRACT]  Path to the ODCS data contract. If omitted, searches for a single    │
+│                             `*.odcs.yaml` in the current directory and its subdirectories.       │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
+│ --project-dir                                  PATH                 Path to the dbt project root │
+│                                                                     (must contain                │
+│                                                                     `dbt_project.yml`). Defaults │
+│                                                                     to the current directory.    │
+│ --schema-name                                  TEXT                 Which ODCS schema object to  │
+│                                                                     sync, by name.               │
+│                                                                     [default: all]               │
+│ --model-resolution                             [name|physicalName]  How to map an ODCS schema to │
+│                                                                     a dbt model name.            │
+│                                                                     [default: name]              │
+│ --target                                       TEXT                 Forwarded to `dbt test       │
+│                                                                     --target`.                   │
+│ --profiles-dir                                 PATH                 Forwarded to `dbt test       │
+│                                                                     --profiles-dir`.             │
+│ --skip-tests          --run-tests                                   Generate tests but skip      │
+│                                                                     running `dbt test`.          │
+│                                                                     [default: run-tests]         │
+│ --publish                                      TEXT                 The url to publish the       │
+│                                                                     results after the test.      │
+│ --server                                       TEXT                 ODCS server name for         │
+│                                                                     published test results.      │
+│                                                                     Auto-selected if the         │
+│                                                                     contract contains only one   │
+│                                                                     server. Otherwise defaults   │
+│                                                                     to --target.                 │
+│ --ssl-verification    --no-ssl-verification                         SSL verification when        │
+│                                                                     publishing test results.     │
+│                                                                     [default: ssl-verification]  │
+│ --debug               --no-debug                                    Enable debug logging         │
+│ --help                                                              Show this message and exit.  │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+                                                                                                    
+ Example: datacontract dbt sync orders.odcs.yaml --project-dir ./warehouse                          
+                                                                                                    
+
+```
+
+`datacontract dbt sync` generates dbt tests from an ODCS data contract directly into your dbt project and (by default) runs `dbt test` against them. The contract becomes the single source of truth for column-level constraints and quality checks. It is recommended to remove existing dbt tests to avoid duplication.
+
+On each run, the command:
+
+- **Wipes and regenerates** the `models/datacontract_cli/` and `tests/datacontract_cli/` directories under your dbt project. The paths honor `model-paths` and `test-paths` in `dbt_project.yml`.
+- **Emits one YAML model file per ODCS schema** that uses dbt's built-in tests and [`dbt_utils`](https://github.com/dbt-labs/dbt-utils).
+- **Emits singular SQL tests** for all ODCS `quality` that can't be expressed as native YAML tests.
+- **Runs `dbt test --select tag:datacontract_cli`** to run the generated tests; pre-existing dbt tests are untouched. Pass `--skip-tests` to regenerate without invoking dbt.
+
+Prerequisites: `dbt-core` plus an adapter (e.g. `dbt-duckdb`, `dbt-postgres`) on `PATH`, [`dbt_utils`](https://github.com/dbt-labs/dbt-utils) installed in your dbt project's `packages.yml`.
+
+```bash
+# Auto-discover a contract named *.odcs.yaml in a dbt project
+$ datacontract dbt sync
+
+# Explicit contract, run against a specific dbt target
+$ datacontract dbt sync orders.odcs.yaml --project-dir ./warehouse --target dev
+
+# Only generate dbt tests, don't run them
+$ datacontract dbt sync orders.odcs.yaml --skip-tests
+
+# Run and publish results to an Entropy Data instance
+$ datacontract dbt sync orders.odcs.yaml --publish https://api.entropy-data.com/api/test-results
+```
+
 ### ci
 ```
                                                                                                     
@@ -1273,6 +1410,9 @@ models:
 │ --help                                                                Show this message and      │
 │                                                                       exit.                      │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+                                                                                                    
+ Example: datacontract ci datacontract.yaml --output test-results.xml --output-format junit         
+                                                                                                    
 
 ```
 
@@ -1397,7 +1537,7 @@ steps:
                                                                                                     
  Example: datacontract export html datacontract.yaml --output datacontract.html                     
  For SQL dialects (postgres, mysql, snowflake, databricks, sqlserver, trino, oracle), use           
- `datacontract export sql --dialect <dialect>`.                                                 
+ `datacontract export sql --dialect <dialect>`.                                                     
                                                                                                     
 
 ```
@@ -1744,9 +1884,9 @@ For more information about the Excel template structure, visit the [ODCS Excel T
 │ --help          Show this message and exit.                                                      │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
 ╭─ Commands ───────────────────────────────────────────────────────────────────────────────────────╮
+│ dbt         Import a data contract from a dbt manifest file.                                     │
 │ sql         Import a data contract from a SQL DDL file.                                          │
 │ avro        Import a data contract from an Avro schema file.                                     │
-│ dbt         Import a data contract from a dbt manifest file.                                     │
 │ dbml        Import a data contract from a DBML file.                                             │
 │ glue        Import a data contract from AWS Glue.                                                │
 │ bigquery    Import a data contract from BigQuery.                                                │
@@ -2136,9 +2276,9 @@ Create a data contract based on the actual data. This is the fastest way to get
 
 4. Set up a CI pipeline that executes daily for continuous quality checks. Use the [`ci`](#ci) command for
    CI-optimized output (GitHub Actions annotations and step summary, Azure DevOps annotations).
-   You can also report the test results to tools like [Data Mesh Manager](https://datamesh-manager.com).
+   You can also report the test results to tools like [Entropy Data](https://entropy-data.com).
    ```bash
-   $ datacontract ci --publish https://api.datamesh-manager.com/api/test-results
+   $ datacontract ci --publish https://api.entropy-data.com/api/test-results
    ```
 
 ### Contract-First

{datacontract_cli-0.12.2 → datacontract_cli-0.12.3}/README.md

@@ -126,6 +126,9 @@ $ datacontract changelog v1.odcs.yaml v2.odcs.yaml
 # execute schema and quality checks (define credentials as environment variables)
 $ datacontract test odcs.yaml
 
+# generate dbt tests from a contract into your dbt project and run `dbt test`
+$ datacontract dbt sync orders.odcs.yaml --project-dir ./warehouse
+
 # export data contract as html (other formats: avro, dbt-models, dbt-sources, dbt-staging-sql, jsonschema, odcs, rdf, sql, sodacl, terraform, ...)
 $ datacontract export html datacontract.yaml --output odcs.html
 
@@ -255,6 +258,7 @@ A list of available extras:
 | PostgreSQL Integration  | `pip install datacontract-cli[postgres]`   |
 | protobuf                | `pip install datacontract-cli[protobuf]`   |
 | RDF                     | `pip install datacontract-cli[rdf]`        |
+| Amazon Redshift         | `pip install datacontract-cli[redshift]`   |
 | S3 Integration          | `pip install datacontract-cli[s3]`         |
 | Snowflake Integration   | `pip install datacontract-cli[snowflake]`  |
 | Microsoft SQL Server    | `pip install datacontract-cli[sqlserver]`  |
@@ -270,6 +274,7 @@ Commands
 - [lint](#lint)
 - [changelog](#changelog)
 - [test](#test)
+- [dbt](#dbt-sync)
 - [ci](#ci)
 - [export](#export)
 - [import](#import)
@@ -340,13 +345,19 @@ Commands
  Show a changelog between two data contracts.                                                       
                                                                                                     
 ╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────╮
-│ *    v1      TEXT  The location (path) of the source (before) data contract YAML. [required]     │
-│ *    v2      TEXT  The location (path) of the target (after) data contract YAML. [required]      │
+│ *    v1      TEXT  The location (url or path) of the source (before) data contract YAML.         │
+│                    [required]                                                                    │
+│ *    v2      TEXT  The location (url or path) of the target (after) data contract YAML.          │
+│                    [required]                                                                    │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
 ╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
 │ --debug    --no-debug      Enable debug logging                                                  │
 │ --help                     Show this message and exit.                                           │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+                                                                                                    
+ Example: datacontract changelog datacontract-v1.yaml datacontract-v2.yaml                          
+                                                                                                    
+
 ```
 
 ```bash
@@ -940,6 +951,52 @@ models:
 
 </details>
 
+<details markdown="1">
+<summary><strong>Amazon Redshift</strong></summary>
+
+Data Contract CLI can test data in Amazon Redshift (both provisioned clusters and Redshift Serverless).
+
+##### Example
+
+datacontract.yaml
+```yaml
+servers:
+  redshift:
+    type: redshift
+    host: my-workgroup.123456789012.us-east-1.redshift-serverless.amazonaws.com
+    port: 5439
+    database: dev
+    schema: analytics
+models:
+  my_table_1: # corresponds to a table
+    type: table
+    fields:
+      my_column_1: # corresponds to a column
+        type: varchar
+```
+
+##### Environment Variables
+All [parameters supported by Soda](https://docs.soda.io/soda/connect-redshift.html), uppercased and prepended by `DATACONTRACT_REDSHIFT_` prefix.
+For example:
+
+| Soda parameter      | Environment Variable                      | Details             |
+|---------------------|-------------------------------------------|---------------------|
+| `username`          | `DATACONTRACT_REDSHIFT_USERNAME`          |                     |
+| `password`          | `DATACONTRACT_REDSHIFT_PASSWORD`          | leave unset for IAM |
+| `region`            | `DATACONTRACT_REDSHIFT_REGION`            | for IAM             |
+| `access_key_id`     | `DATACONTRACT_REDSHIFT_ACCESS_KEY_ID`     | for IAM             |
+| `secret_access_key` | `DATACONTRACT_REDSHIFT_SECRET_ACCESS_KEY` | for IAM             |
+| `role_arn`          | `DATACONTRACT_REDSHIFT_ROLE_ARN`          | for IAM             |
+
+IAM credentials can be supplied in two ways:
+
+1. **AWS_PROFILE** — set `AWS_PROFILE` in your shell to a profile defined in `~/.aws/credentials` and `DATACONTRACT_REDSHIFT_REGION`.
+2. **Explicit keys** — set `DATACONTRACT_REDSHIFT_REGION`, `..._ACCESS_KEY_ID`, `..._SECRET_ACCESS_KEY`, and `..._SESSION_TOKEN` for temporary credentials, or `..._ROLE_ARN` to assume a role.
+
+>IAM authentication is supported only for **provisioned** Redshift clusters.
+
+</details>
+
 <details markdown="1">
 <summary><strong>MySQL</strong></summary>
 
@@ -1119,6 +1176,84 @@ models:
 
 </details>
 
+### dbt sync
+> The `dbt sync` command is still work in progress and will receive further functionality and documentation soon.
+```
+                                                                                                    
+ Usage: datacontract dbt sync [OPTIONS] [CONTRACT]                                                  
+                                                                                                    
+ Generate dbt tests from an ODCS contract and run them.                                             
+                                                                                                    
+ Within the specified dbt project, this command wipes `<model-paths>/datacontract_cli/` and         
+ `<test-paths>/datacontract_cli/`, regenerates them from the contract, then runs `dbt test`.        
+                                                                                                    
+╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────╮
+│   contract      [CONTRACT]  Path to the ODCS data contract. If omitted, searches for a single    │
+│                             `*.odcs.yaml` in the current directory and its subdirectories.       │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
+│ --project-dir                                  PATH                 Path to the dbt project root │
+│                                                                     (must contain                │
+│                                                                     `dbt_project.yml`). Defaults │
+│                                                                     to the current directory.    │
+│ --schema-name                                  TEXT                 Which ODCS schema object to  │
+│                                                                     sync, by name.               │
+│                                                                     [default: all]               │
+│ --model-resolution                             [name|physicalName]  How to map an ODCS schema to │
+│                                                                     a dbt model name.            │
+│                                                                     [default: name]              │
+│ --target                                       TEXT                 Forwarded to `dbt test       │
+│                                                                     --target`.                   │
+│ --profiles-dir                                 PATH                 Forwarded to `dbt test       │
+│                                                                     --profiles-dir`.             │
+│ --skip-tests          --run-tests                                   Generate tests but skip      │
+│                                                                     running `dbt test`.          │
+│                                                                     [default: run-tests]         │
+│ --publish                                      TEXT                 The url to publish the       │
+│                                                                     results after the test.      │
+│ --server                                       TEXT                 ODCS server name for         │
+│                                                                     published test results.      │
+│                                                                     Auto-selected if the         │
+│                                                                     contract contains only one   │
+│                                                                     server. Otherwise defaults   │
+│                                                                     to --target.                 │
+│ --ssl-verification    --no-ssl-verification                         SSL verification when        │
+│                                                                     publishing test results.     │
+│                                                                     [default: ssl-verification]  │
+│ --debug               --no-debug                                    Enable debug logging         │
+│ --help                                                              Show this message and exit.  │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+                                                                                                    
+ Example: datacontract dbt sync orders.odcs.yaml --project-dir ./warehouse                          
+                                                                                                    
+
+```
+
+`datacontract dbt sync` generates dbt tests from an ODCS data contract directly into your dbt project and (by default) runs `dbt test` against them. The contract becomes the single source of truth for column-level constraints and quality checks. It is recommended to remove existing dbt tests to avoid duplication.
+
+On each run, the command:
+
+- **Wipes and regenerates** the `models/datacontract_cli/` and `tests/datacontract_cli/` directories under your dbt project. The paths honor `model-paths` and `test-paths` in `dbt_project.yml`.
+- **Emits one YAML model file per ODCS schema** that uses dbt's built-in tests and [`dbt_utils`](https://github.com/dbt-labs/dbt-utils).
+- **Emits singular SQL tests** for all ODCS `quality` that can't be expressed as native YAML tests.
+- **Runs `dbt test --select tag:datacontract_cli`** to run the generated tests; pre-existing dbt tests are untouched. Pass `--skip-tests` to regenerate without invoking dbt.
+
+Prerequisites: `dbt-core` plus an adapter (e.g. `dbt-duckdb`, `dbt-postgres`) on `PATH`, [`dbt_utils`](https://github.com/dbt-labs/dbt-utils) installed in your dbt project's `packages.yml`.
+
+```bash
+# Auto-discover a contract named *.odcs.yaml in a dbt project
+$ datacontract dbt sync
+
+# Explicit contract, run against a specific dbt target
+$ datacontract dbt sync orders.odcs.yaml --project-dir ./warehouse --target dev
+
+# Only generate dbt tests, don't run them
+$ datacontract dbt sync orders.odcs.yaml --skip-tests
+
+# Run and publish results to an Entropy Data instance
+$ datacontract dbt sync orders.odcs.yaml --publish https://api.entropy-data.com/api/test-results
+```
+
 ### ci
 ```
                                                                                                     
@@ -1169,6 +1304,9 @@ models:
 │ --help                                                                Show this message and      │
 │                                                                       exit.                      │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
+                                                                                                    
+ Example: datacontract ci datacontract.yaml --output test-results.xml --output-format junit         
+                                                                                                    
 
 ```
 
@@ -1293,7 +1431,7 @@ steps:
                                                                                                     
  Example: datacontract export html datacontract.yaml --output datacontract.html                     
  For SQL dialects (postgres, mysql, snowflake, databricks, sqlserver, trino, oracle), use           
- `datacontract export sql --dialect <dialect>`.                                                 
+ `datacontract export sql --dialect <dialect>`.                                                     
                                                                                                     
 
 ```
@@ -1640,9 +1778,9 @@ For more information about the Excel template structure, visit the [ODCS Excel T
 │ --help          Show this message and exit.                                                      │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
 ╭─ Commands ───────────────────────────────────────────────────────────────────────────────────────╮
+│ dbt         Import a data contract from a dbt manifest file.                                     │
 │ sql         Import a data contract from a SQL DDL file.                                          │
 │ avro        Import a data contract from an Avro schema file.                                     │
-│ dbt         Import a data contract from a dbt manifest file.                                     │
 │ dbml        Import a data contract from a DBML file.                                             │
 │ glue        Import a data contract from AWS Glue.                                                │
 │ bigquery    Import a data contract from BigQuery.                                                │
@@ -2032,9 +2170,9 @@ Create a data contract based on the actual data. This is the fastest way to get
 
 4. Set up a CI pipeline that executes daily for continuous quality checks. Use the [`ci`](#ci) command for
    CI-optimized output (GitHub Actions annotations and step summary, Azure DevOps annotations).
-   You can also report the test results to tools like [Data Mesh Manager](https://datamesh-manager.com).
+   You can also report the test results to tools like [Entropy Data](https://entropy-data.com).
    ```bash
-   $ datacontract ci --publish https://api.datamesh-manager.com/api/test-results
+   $ datacontract ci --publish https://api.entropy-data.com/api/test-results
    ```
 
 ### Contract-First

{datacontract_cli-0.12.2 → datacontract_cli-0.12.3}/datacontract/cli.py

@@ -15,9 +15,27 @@ console = Console()
 debug_option = Annotated[bool, typer.Option(help="Enable debug logging")]
 
 
+# Order in which top-level commands appear in `datacontract --help` (cf. README.md)
+COMMAND_ORDER = [
+    "init",
+    "lint",
+    "changelog",
+    "test",
+    "ci",
+    "export",
+    "dbt",
+    "import",
+    "catalog",
+    "publish",
+    "api",
+]
+
+
 class OrderedCommands(TyperGroup):
     def list_commands(self, ctx: Context) -> Iterable[str]:
-        return self.commands.keys()
+        known = set(COMMAND_ORDER)
+        # Trailing fallback keeps any future command visible even if COMMAND_ORDER forgets it.
+        return [c for c in COMMAND_ORDER if c in self.commands] + [c for c in self.commands if c not in known]
 
 
 class OrderedCommandsWithMigrationHints(OrderedCommands):
@@ -105,10 +123,21 @@ def common(
 
 
 def enable_debug_logging(debug: bool):
+    root = logging.getLogger()
     if debug:
         logging.basicConfig(
             level=logging.DEBUG, format="%(asctime)s - %(name)s - %(levelname)s - %(message)s", stream=sys.stderr
         )
+    elif not root.handlers:
+        # Without a handler, Python's lastResort emits WARNING/ERROR messages
+        root.addHandler(logging.NullHandler())
+
+
+def validate_publish_url(publish: str | None) -> None:
+    """Reject `--publish` values that aren't http/https before any real work runs."""
+    if publish is not None and not (publish.startswith("http://") or publish.startswith("https://")):
+        console.print(f"[red]--publish URL must start with http:// or https:// (got: {publish!r}).[/red]")
+        raise typer.Exit(code=1)
 
 
 def _print_logs(run, out=None):
@@ -123,11 +152,13 @@ def _print_logs(run, out=None):
 # Register commands (must be after app and shared helpers are defined so the
 # command_* modules can import from this module without circular-import issues)
 # ---------------------------------------------------------------------------
+# Display order for `--help` is controlled by COMMAND_ORDER above, not by import order.
 from datacontract import (  # noqa: E402, F401
     command_api,
     command_catalog,
     command_changelog,
     command_ci,
+    command_dbt,
     command_export,
     command_import,
     command_init,
@@ -136,7 +167,6 @@ from datacontract import (  # noqa: E402, F401
     command_test,
 )
 
-# Commands with subcommands
 app.add_typer(
     command_import.import_app,
     name="import",
@@ -153,6 +183,12 @@ app.add_typer(
         "use `datacontract export sql --dialect <dialect>`."
     ),
 )
+app.add_typer(
+    command_dbt.dbt_app,
+    name="dbt",
+    help="Work with data contracts in your dbt project.",
+    epilog="Example: datacontract dbt sync orders.odcs.yaml --project-dir ./warehouse",
+)
 
 
 def main():
@@ -162,7 +198,10 @@ def main():
         # If an uncaught exception occurs, only print its name (except when debug mode is enabled)
         if "--debug" in sys.argv or os.environ.get("DATACONTRACT_CLI_DEBUG") == "1":
             raise
-        console.print(f"[red]Error:[/red] {e}")
+        from datacontract.model.exceptions import DataContractException
+
+        message = e.reason if isinstance(e, DataContractException) else str(e)
+        console.print(f"[red]Error:[/red] {message}")
         console.print("[dim]Pass --debug (or set DATACONTRACT_CLI_DEBUG=1) for the full traceback.[/dim]")
         sys.exit(1)
 

{datacontract_cli-0.12.2 → datacontract_cli-0.12.3}/datacontract/command_ci.py

@@ -6,7 +6,7 @@ import typer
 from rich.console import Console
 from typing_extensions import Annotated
 
-from datacontract.cli import _print_logs, app, console, debug_option, enable_debug_logging
+from datacontract.cli import _print_logs, app, console, debug_option, enable_debug_logging, validate_publish_url
 from datacontract.data_contract import DataContract
 from datacontract.output.ci_output import write_ci_output, write_ci_summary, write_json_results
 from datacontract.output.output_format import OutputFormat
@@ -65,6 +65,7 @@ def ci(
     Run tests for CI/CD pipelines. Emits GitHub Actions annotations and step summary.
     """
     enable_debug_logging(debug)
+    validate_publish_url(publish)
 
     if not locations:
         locations = ["datacontract.yaml"]