datacontract-cli 0.10.15__tar.gz → 0.10.18__tar.gz

{datacontract_cli-0.10.15/datacontract_cli.egg-info → datacontract_cli-0.10.18}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.2
 Name: datacontract-cli
-Version: 0.10.15
+Version: 0.10.18
 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>
 Project-URL: Homepage, https://cli.datacontract.com
@@ -11,72 +11,72 @@ Classifier: Operating System :: OS Independent
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: typer<0.14,>=0.12
-Requires-Dist: pydantic<2.10.0,>=2.8.2
+Requires-Dist: typer<0.16,>=0.15.1
+Requires-Dist: pydantic<2.11.0,>=2.8.2
 Requires-Dist: pyyaml~=6.0.1
 Requires-Dist: requests<2.33,>=2.31
-Requires-Dist: fastapi==0.115.5
-Requires-Dist: uvicorn==0.32.1
-Requires-Dist: fastjsonschema<2.21.0,>=2.19.1
-Requires-Dist: fastparquet==2024.5.0
-Requires-Dist: python-multipart==0.0.12
+Requires-Dist: fastapi==0.115.6
+Requires-Dist: uvicorn==0.34.0
+Requires-Dist: fastjsonschema<2.22.0,>=2.19.1
+Requires-Dist: fastparquet==2024.11.0
+Requires-Dist: numpy<2.0.0,>=1.26.4
+Requires-Dist: python-multipart==0.0.20
 Requires-Dist: rich<13.10,>=13.7
 Requires-Dist: simple-ddl-parser==1.7.1
 Requires-Dist: duckdb==1.1.2
-Requires-Dist: soda-core-duckdb<3.5.0,>=3.3.1
+Requires-Dist: soda-core-duckdb<3.4.0,>=3.3.20
 Requires-Dist: setuptools>=60
 Requires-Dist: python-dotenv~=1.0.0
 Requires-Dist: rdflib==7.0.0
-Requires-Dist: opentelemetry-exporter-otlp-proto-grpc~=1.16
-Requires-Dist: opentelemetry-exporter-otlp-proto-http~=1.16
-Requires-Dist: boto3<1.35.69,>=1.34.41
+Requires-Dist: boto3<1.35.98,>=1.34.41
 Requires-Dist: jinja_partials>=0.2.1
 Provides-Extra: avro
 Requires-Dist: avro==1.12.0; extra == "avro"
 Provides-Extra: bigquery
-Requires-Dist: soda-core-bigquery<3.5.0,>=3.3.1; extra == "bigquery"
+Requires-Dist: soda-core-bigquery<3.4.0,>=3.3.20; extra == "bigquery"
 Provides-Extra: databricks
-Requires-Dist: soda-core-spark-df<3.5.0,>=3.3.1; extra == "databricks"
-Requires-Dist: databricks-sql-connector<3.6.0,>=3.1.2; extra == "databricks"
-Requires-Dist: databricks-sdk<0.39.0,>=0.32.0; extra == "databricks"
-Requires-Dist: soda-core-spark[databricks]<3.5.0,>=3.3.1; extra == "databricks"
+Requires-Dist: soda-core-spark-df<3.4.0,>=3.3.20; extra == "databricks"
+Requires-Dist: soda-core-spark[databricks]<3.4.0,>=3.3.20; extra == "databricks"
+Requires-Dist: databricks-sql-connector<3.8.0,>=3.7.0; extra == "databricks"
+Requires-Dist: databricks-sdk<0.41.0; extra == "databricks"
 Provides-Extra: iceberg
-Requires-Dist: pyiceberg==0.7.1; extra == "iceberg"
+Requires-Dist: pyiceberg==0.8.1; extra == "iceberg"
 Provides-Extra: kafka
 Requires-Dist: datacontract-cli[avro]; extra == "kafka"
-Requires-Dist: soda-core-spark-df<3.5.0,>=3.3.1; extra == "kafka"
+Requires-Dist: soda-core-spark-df<3.4.0,>=3.3.20; extra == "kafka"
 Provides-Extra: postgres
-Requires-Dist: soda-core-postgres<3.5.0,>=3.3.1; extra == "postgres"
+Requires-Dist: soda-core-postgres<3.4.0,>=3.3.20; extra == "postgres"
 Provides-Extra: s3
-Requires-Dist: s3fs==2024.10.0; extra == "s3"
+Requires-Dist: s3fs==2024.12.0; extra == "s3"
+Requires-Dist: aiobotocore<2.18.0,>=2.17.0; extra == "s3"
 Provides-Extra: snowflake
 Requires-Dist: snowflake-connector-python[pandas]<3.13,>=3.6; extra == "snowflake"
-Requires-Dist: soda-core-snowflake<3.5.0,>=3.3.1; extra == "snowflake"
+Requires-Dist: soda-core-snowflake<3.4.0,>=3.3.20; extra == "snowflake"
 Provides-Extra: sqlserver
-Requires-Dist: soda-core-sqlserver<3.5.0,>=3.3.1; extra == "sqlserver"
+Requires-Dist: soda-core-sqlserver<3.4.0,>=3.3.20; extra == "sqlserver"
 Provides-Extra: trino
-Requires-Dist: soda-core-trino<3.5.0,>=3.3.1; extra == "trino"
+Requires-Dist: soda-core-trino<3.4.0,>=3.3.20; extra == "trino"
 Provides-Extra: dbt
 Requires-Dist: dbt-core>=1.8.0; extra == "dbt"
 Provides-Extra: dbml
 Requires-Dist: pydbml>=1.1.1; extra == "dbml"
 Provides-Extra: parquet
-Requires-Dist: pyarrow>=12.0.0; extra == "parquet"
+Requires-Dist: pyarrow>=18.1.0; extra == "parquet"
 Provides-Extra: all
 Requires-Dist: datacontract-cli[bigquery,databricks,dbml,dbt,iceberg,kafka,parquet,postgres,s3,snowflake,sqlserver,trino]; extra == "all"
 Provides-Extra: dev
 Requires-Dist: datacontract-cli[all]; extra == "dev"
-Requires-Dist: httpx==0.27.2; extra == "dev"
+Requires-Dist: httpx==0.28.1; extra == "dev"
 Requires-Dist: kafka-python; extra == "dev"
-Requires-Dist: moto==5.0.18; extra == "dev"
+Requires-Dist: moto==5.0.26; extra == "dev"
 Requires-Dist: pandas>=2.1.0; extra == "dev"
 Requires-Dist: pre-commit<4.1.0,>=3.7.1; extra == "dev"
 Requires-Dist: pytest; extra == "dev"
 Requires-Dist: pytest-xdist; extra == "dev"
-Requires-Dist: pymssql==2.3.1; extra == "dev"
+Requires-Dist: pymssql==2.3.2; extra == "dev"
 Requires-Dist: ruff; extra == "dev"
-Requires-Dist: testcontainers[kafka,minio,mssql,postgres]==4.8.2; extra == "dev"
-Requires-Dist: trino==0.330.0; extra == "dev"
+Requires-Dist: testcontainers[kafka,minio,mssql,postgres]==4.9.0; extra == "dev"
+Requires-Dist: trino==0.331.0; extra == "dev"
 
 # Data Contract CLI
 
@@ -105,7 +105,7 @@ This data contract contains all information to connect to S3 and check that the
 
 Let's use [pip](https://pip.pypa.io/en/stable/getting-started/) to install the CLI (or use the [Docker image](#docker)),
 ```bash
-$ python3 -m pip install datacontract-cli[all]
+$ python3 -m pip install 'datacontract-cli[all]'
 ```
 
 
@@ -230,13 +230,13 @@ Choose the most appropriate installation method for your needs:
 Python 3.10, 3.11, and 3.12 are supported. We recommend to use Python 3.11.
 
 ```bash
-python3 -m pip install datacontract-cli[all]
+python3 -m pip install 'datacontract-cli[all]'
 ```
 
 ### pipx
 pipx installs into an isolated environment.
 ```bash
-pipx install datacontract-cli[all]
+pipx install 'datacontract-cli[all]'
 ```
 
 ### Docker
@@ -301,6 +301,7 @@ Commands
 - [diff](#diff)
 - [catalog](#catalog)
 - [publish](#publish)
+- [serve](#serve)
 
 ### init
 
@@ -365,9 +366,6 @@ Commands
 │                                                                      [default: no-examples]                                     │
 │ --publish                                                      TEXT  The url to publish the results after the test              │
 │                                                                      [default: None]                                            │
-│ --publish-to-opentelemetry    --no-publish-to-opentelemetry          Publish the results to opentelemetry. Use environment      │
-│                                                                      variables to configure the OTLP endpoint, headers, etc.    │
-│                                                                      [default: no-publish-to-opentelemetry]                     │
 │ --logs                        --no-logs                              Print logs [default: no-logs]                              │
 │ --help                                                               Show this message and exit.                                │
 ╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
@@ -592,7 +590,6 @@ datacontract.yaml
 servers:
   production:
     type: databricks
-    host: dbc-abcdefgh-1234.cloud.databricks.com
     catalog: acme_catalog_prod
     schema: orders_latest
 models:
@@ -603,10 +600,11 @@ models:
 
 #### Environment Variables
 
-| Environment Variable                         | Example                              | Description                                           |
-|----------------------------------------------|--------------------------------------|-------------------------------------------------------|
-| `DATACONTRACT_DATABRICKS_TOKEN`              | `dapia00000000000000000000000000000` | The personal access token to authenticate             |
-| `DATACONTRACT_DATABRICKS_HTTP_PATH`          | `/sql/1.0/warehouses/b053a3ffffffff` | The HTTP path to the SQL warehouse or compute cluster |
+| Environment Variable                      | Example                              | Description                                               |
+|-------------------------------------------|--------------------------------------|-----------------------------------------------------------|
+| `DATACONTRACT_DATABRICKS_TOKEN`           | `dapia00000000000000000000000000000` | The personal access token to authenticate                 |
+| `DATACONTRACT_DATABRICKS_HTTP_PATH`       | `/sql/1.0/warehouses/b053a3ffffffff` | The HTTP path to the SQL warehouse or compute cluster     |
+| `DATACONTRACT_DATABRICKS_SERVER_HOSTNAME` | `dbc-abcdefgh-1234.cloud.databricks.com` | The host name of the SQL warehouse or compute cluster |
 
 
 ### Databricks (programmatic)
@@ -841,7 +839,7 @@ models:
 │                    t-staging-sql|odcs|odcs_v2|odcs_v3|rdf|avro|protobuf                                                        │
 │                    |great-expectations|terraform|avro-idl|sql|sql-query                                                        │
 │                    |html|go|bigquery|dbml|spark|sqlalchemy|data-caterer                                                        │
-│                    |dcs]                                                                                                       │
+│                    |dcs|markdown|iceberg]                                                                                              │
 │    --output        PATH                                                  Specify the file path where the exported data will be │
 │                                                                          saved. If no path is provided, the output will be     │
 │                                                                          printed to stdout.                                    │
@@ -902,6 +900,8 @@ Available export options:
 | `sqlalchemy`         | Export to SQLAlchemy Models                             | ✅      |
 | `data-caterer`       | Export to Data Caterer in YAML format                   | ✅      |
 | `dcs`                | Export to Data Contract Specification in YAML format    | ✅      |
+| `markdown`           | Export to Markdown                                      | ✅      |
+| `iceberg`            | Export to an Iceberg JSON Schema Definition             | partial |
 | Missing something?   | Please create an issue on GitHub                        | TBD    |
 
 
@@ -1025,6 +1025,63 @@ models:
     - **avroLogicalType**: Specifies the logical type of the field in Avro. In this example, it is `local-timestamp-micros`.
     - **avroDefault**: Specifies the default value for the field in Avro. In this example, it is 1672534861000000 which corresponds to ` 2023-01-01 01:01:01 UTC`.
 
+#### Iceberg
+
+Exports to an [Iceberg Table Json Schema Definition](https://iceberg.apache.org/spec/#appendix-c-json-serialization).
+
+This export only supports a single model export at a time because Iceberg's schema definition is for a single table and the exporter maps 1 model to 1 table, use the `--model` flag
+to limit your contract export to a single model.
+
+```bash
+ $ datacontract export --format iceberg --model orders https://datacontract.com/examples/orders-latest/datacontract.yaml --output /tmp/orders_iceberg.json
+ 
+ $ cat /tmp/orders_iceberg.json | jq '.'
+{
+  "type": "struct",
+  "fields": [
+    {
+      "id": 1,
+      "name": "order_id",
+      "type": "string",
+      "required": true
+    },
+    {
+      "id": 2,
+      "name": "order_timestamp",
+      "type": "timestamptz",
+      "required": true
+    },
+    {
+      "id": 3,
+      "name": "order_total",
+      "type": "long",
+      "required": true
+    },
+    {
+      "id": 4,
+      "name": "customer_id",
+      "type": "string",
+      "required": false
+    },
+    {
+      "id": 5,
+      "name": "customer_email_address",
+      "type": "string",
+      "required": true
+    },
+    {
+      "id": 6,
+      "name": "processed_timestamp",
+      "type": "timestamptz",
+      "required": true
+    }
+  ],
+  "schema-id": 0,
+  "identifier-field-ids": [
+    1
+  ]
+}
+```
 
 ### import
 
@@ -1331,13 +1388,28 @@ datacontract catalog --files "*.odcs.yaml"
 ╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
 ```
 
+### Serve
+
+```
+
+ Usage: datacontract serve [OPTIONS]
+
+ Start the datacontract web server.
+
+╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ --port        INTEGER  Bind socket to this port. [default: 4242]                                                           │
+│ --host        TEXT     Bind socket to this host. [default: 127.0.0.1]                                                      │
+│ --help                 Show this message and exit.                                                                         │
+╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+
+```
+
 ## Integrations
 
 | Integration           | Option                       | Description                                                                                                   |
 |-----------------------|------------------------------|---------------------------------------------------------------------------------------------------------------|
 | Data Mesh Manager     | `--publish`                  | Push full results to the [Data Mesh Manager API](https://api.datamesh-manager.com/swagger/index.html)         |
 | Data Contract Manager | `--publish`                  | Push full results to the [Data Contract Manager API](https://api.datacontract-manager.com/swagger/index.html) |
-| OpenTelemetry         | `--publish-to-opentelemetry` | Push result as gauge metrics                                                                                  |
 
 ### Integration with Data Mesh Manager
 
@@ -1351,36 +1423,6 @@ $ datacontract test https://demo.datamesh-manager.com/demo279750347121/datacontr
  --publish https://api.datamesh-manager.com/api/test-results
 ```
 
-### Integration with OpenTelemetry
-
-If you use OpenTelemetry, you can use the data contract URL and append the `--publish-to-opentelemetry` option to send the test results to your OLTP-compatible instance, e.g., Prometheus.
-
-The metric name is "datacontract.cli.test.result" and it uses the following encoding for the result:
-
-| datacontract.cli.test.result | Description                           |
-|------------------------------|---------------------------------------|
-| 0                            | test run passed, no warnings          |
-| 1                            | test run has warnings                 |
-| 2                            | test run failed                       |
-| 3                            | test run not possible due to an error |
-| 4                            | test status unknown                   |
-
-
-```bash
-# Fetch current data contract, execute tests on production, and publish result to open telemetry
-$ EXPORT OTEL_SERVICE_NAME=datacontract-cli
-$ EXPORT OTEL_EXPORTER_OTLP_ENDPOINT=https://YOUR_ID.apm.westeurope.azure.elastic-cloud.com:443
-$ EXPORT OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20secret # Optional, when using SaaS Products
-$ EXPORT OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf # Optional, default is http/protobuf - use value grpc to use the gRPC protocol instead
-# Send to OpenTelemetry
-$ datacontract test https://demo.datamesh-manager.com/demo279750347121/datacontracts/4df9d6ee-e55d-4088-9598-b635b2fdcbbc/datacontract.yaml --server production --publish-to-opentelemetry
-```
-
-Current limitations:
-- currently, only ConsoleExporter and OTLP Exporter
-- Metrics only, no logs yet (but loosely planned)
-
-
 ## Best Practices
 
 We share best practices in using the Data Contract CLI.
@@ -1412,7 +1454,7 @@ Create a data contract based on the actual data. This is the fastest way to get
    $ datacontract lint
    ```
 
-5. Set up a CI pipeline that executes daily and reports the results to the [Data Mesh Manager](https://datamesh-manager.com). Or to some place else. You can even publish to any opentelemetry compatible system.
+5. Set up a CI pipeline that executes daily for continuous quality checks. You can also report the test results to tools like [Data Mesh Manager](https://datamesh-manager.com) 
    ```bash
    $ datacontract test --publish https://api.datamesh-manager.com/api/test-results
    ```

{datacontract_cli-0.10.15 → datacontract_cli-0.10.18}/README.md

@@ -25,7 +25,7 @@ This data contract contains all information to connect to S3 and check that the
 
 Let's use [pip](https://pip.pypa.io/en/stable/getting-started/) to install the CLI (or use the [Docker image](#docker)),
 ```bash
-$ python3 -m pip install datacontract-cli[all]
+$ python3 -m pip install 'datacontract-cli[all]'
 ```
 
 
@@ -150,13 +150,13 @@ Choose the most appropriate installation method for your needs:
 Python 3.10, 3.11, and 3.12 are supported. We recommend to use Python 3.11.
 
 ```bash
-python3 -m pip install datacontract-cli[all]
+python3 -m pip install 'datacontract-cli[all]'
 ```
 
 ### pipx
 pipx installs into an isolated environment.
 ```bash
-pipx install datacontract-cli[all]
+pipx install 'datacontract-cli[all]'
 ```
 
 ### Docker
@@ -221,6 +221,7 @@ Commands
 - [diff](#diff)
 - [catalog](#catalog)
 - [publish](#publish)
+- [serve](#serve)
 
 ### init
 
@@ -285,9 +286,6 @@ Commands
 │                                                                      [default: no-examples]                                     │
 │ --publish                                                      TEXT  The url to publish the results after the test              │
 │                                                                      [default: None]                                            │
-│ --publish-to-opentelemetry    --no-publish-to-opentelemetry          Publish the results to opentelemetry. Use environment      │
-│                                                                      variables to configure the OTLP endpoint, headers, etc.    │
-│                                                                      [default: no-publish-to-opentelemetry]                     │
 │ --logs                        --no-logs                              Print logs [default: no-logs]                              │
 │ --help                                                               Show this message and exit.                                │
 ╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
@@ -512,7 +510,6 @@ datacontract.yaml
 servers:
   production:
     type: databricks
-    host: dbc-abcdefgh-1234.cloud.databricks.com
     catalog: acme_catalog_prod
     schema: orders_latest
 models:
@@ -523,10 +520,11 @@ models:
 
 #### Environment Variables
 
-| Environment Variable                         | Example                              | Description                                           |
-|----------------------------------------------|--------------------------------------|-------------------------------------------------------|
-| `DATACONTRACT_DATABRICKS_TOKEN`              | `dapia00000000000000000000000000000` | The personal access token to authenticate             |
-| `DATACONTRACT_DATABRICKS_HTTP_PATH`          | `/sql/1.0/warehouses/b053a3ffffffff` | The HTTP path to the SQL warehouse or compute cluster |
+| Environment Variable                      | Example                              | Description                                               |
+|-------------------------------------------|--------------------------------------|-----------------------------------------------------------|
+| `DATACONTRACT_DATABRICKS_TOKEN`           | `dapia00000000000000000000000000000` | The personal access token to authenticate                 |
+| `DATACONTRACT_DATABRICKS_HTTP_PATH`       | `/sql/1.0/warehouses/b053a3ffffffff` | The HTTP path to the SQL warehouse or compute cluster     |
+| `DATACONTRACT_DATABRICKS_SERVER_HOSTNAME` | `dbc-abcdefgh-1234.cloud.databricks.com` | The host name of the SQL warehouse or compute cluster |
 
 
 ### Databricks (programmatic)
@@ -761,7 +759,7 @@ models:
 │                    t-staging-sql|odcs|odcs_v2|odcs_v3|rdf|avro|protobuf                                                        │
 │                    |great-expectations|terraform|avro-idl|sql|sql-query                                                        │
 │                    |html|go|bigquery|dbml|spark|sqlalchemy|data-caterer                                                        │
-│                    |dcs]                                                                                                       │
+│                    |dcs|markdown|iceberg]                                                                                              │
 │    --output        PATH                                                  Specify the file path where the exported data will be │
 │                                                                          saved. If no path is provided, the output will be     │
 │                                                                          printed to stdout.                                    │
@@ -822,6 +820,8 @@ Available export options:
 | `sqlalchemy`         | Export to SQLAlchemy Models                             | ✅      |
 | `data-caterer`       | Export to Data Caterer in YAML format                   | ✅      |
 | `dcs`                | Export to Data Contract Specification in YAML format    | ✅      |
+| `markdown`           | Export to Markdown                                      | ✅      |
+| `iceberg`            | Export to an Iceberg JSON Schema Definition             | partial |
 | Missing something?   | Please create an issue on GitHub                        | TBD    |
 
 
@@ -945,6 +945,63 @@ models:
     - **avroLogicalType**: Specifies the logical type of the field in Avro. In this example, it is `local-timestamp-micros`.
     - **avroDefault**: Specifies the default value for the field in Avro. In this example, it is 1672534861000000 which corresponds to ` 2023-01-01 01:01:01 UTC`.
 
+#### Iceberg
+
+Exports to an [Iceberg Table Json Schema Definition](https://iceberg.apache.org/spec/#appendix-c-json-serialization).
+
+This export only supports a single model export at a time because Iceberg's schema definition is for a single table and the exporter maps 1 model to 1 table, use the `--model` flag
+to limit your contract export to a single model.
+
+```bash
+ $ datacontract export --format iceberg --model orders https://datacontract.com/examples/orders-latest/datacontract.yaml --output /tmp/orders_iceberg.json
+ 
+ $ cat /tmp/orders_iceberg.json | jq '.'
+{
+  "type": "struct",
+  "fields": [
+    {
+      "id": 1,
+      "name": "order_id",
+      "type": "string",
+      "required": true
+    },
+    {
+      "id": 2,
+      "name": "order_timestamp",
+      "type": "timestamptz",
+      "required": true
+    },
+    {
+      "id": 3,
+      "name": "order_total",
+      "type": "long",
+      "required": true
+    },
+    {
+      "id": 4,
+      "name": "customer_id",
+      "type": "string",
+      "required": false
+    },
+    {
+      "id": 5,
+      "name": "customer_email_address",
+      "type": "string",
+      "required": true
+    },
+    {
+      "id": 6,
+      "name": "processed_timestamp",
+      "type": "timestamptz",
+      "required": true
+    }
+  ],
+  "schema-id": 0,
+  "identifier-field-ids": [
+    1
+  ]
+}
+```
 
 ### import
 
@@ -1251,13 +1308,28 @@ datacontract catalog --files "*.odcs.yaml"
 ╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
 ```
 
+### Serve
+
+```
+
+ Usage: datacontract serve [OPTIONS]
+
+ Start the datacontract web server.
+
+╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ --port        INTEGER  Bind socket to this port. [default: 4242]                                                           │
+│ --host        TEXT     Bind socket to this host. [default: 127.0.0.1]                                                      │
+│ --help                 Show this message and exit.                                                                         │
+╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+
+```
+
 ## Integrations
 
 | Integration           | Option                       | Description                                                                                                   |
 |-----------------------|------------------------------|---------------------------------------------------------------------------------------------------------------|
 | Data Mesh Manager     | `--publish`                  | Push full results to the [Data Mesh Manager API](https://api.datamesh-manager.com/swagger/index.html)         |
 | Data Contract Manager | `--publish`                  | Push full results to the [Data Contract Manager API](https://api.datacontract-manager.com/swagger/index.html) |
-| OpenTelemetry         | `--publish-to-opentelemetry` | Push result as gauge metrics                                                                                  |
 
 ### Integration with Data Mesh Manager
 
@@ -1271,36 +1343,6 @@ $ datacontract test https://demo.datamesh-manager.com/demo279750347121/datacontr
  --publish https://api.datamesh-manager.com/api/test-results
 ```
 
-### Integration with OpenTelemetry
-
-If you use OpenTelemetry, you can use the data contract URL and append the `--publish-to-opentelemetry` option to send the test results to your OLTP-compatible instance, e.g., Prometheus.
-
-The metric name is "datacontract.cli.test.result" and it uses the following encoding for the result:
-
-| datacontract.cli.test.result | Description                           |
-|------------------------------|---------------------------------------|
-| 0                            | test run passed, no warnings          |
-| 1                            | test run has warnings                 |
-| 2                            | test run failed                       |
-| 3                            | test run not possible due to an error |
-| 4                            | test status unknown                   |
-
-
-```bash
-# Fetch current data contract, execute tests on production, and publish result to open telemetry
-$ EXPORT OTEL_SERVICE_NAME=datacontract-cli
-$ EXPORT OTEL_EXPORTER_OTLP_ENDPOINT=https://YOUR_ID.apm.westeurope.azure.elastic-cloud.com:443
-$ EXPORT OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20secret # Optional, when using SaaS Products
-$ EXPORT OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf # Optional, default is http/protobuf - use value grpc to use the gRPC protocol instead
-# Send to OpenTelemetry
-$ datacontract test https://demo.datamesh-manager.com/demo279750347121/datacontracts/4df9d6ee-e55d-4088-9598-b635b2fdcbbc/datacontract.yaml --server production --publish-to-opentelemetry
-```
-
-Current limitations:
-- currently, only ConsoleExporter and OTLP Exporter
-- Metrics only, no logs yet (but loosely planned)
-
-
 ## Best Practices
 
 We share best practices in using the Data Contract CLI.
@@ -1332,7 +1374,7 @@ Create a data contract based on the actual data. This is the fastest way to get
    $ datacontract lint
    ```
 
-5. Set up a CI pipeline that executes daily and reports the results to the [Data Mesh Manager](https://datamesh-manager.com). Or to some place else. You can even publish to any opentelemetry compatible system.
+5. Set up a CI pipeline that executes daily for continuous quality checks. You can also report the test results to tools like [Data Mesh Manager](https://datamesh-manager.com) 
    ```bash
    $ datacontract test --publish https://api.datamesh-manager.com/api/test-results
    ```

{datacontract_cli-0.10.15 → datacontract_cli-0.10.18}/datacontract/breaking/breaking.py

@@ -1,6 +1,6 @@
 from datacontract.breaking.breaking_rules import BreakingRules
 from datacontract.model.breaking_change import BreakingChange, Location, Severity
-from datacontract.model.data_contract_specification import Contact, Field, Info, Model, Quality, Terms
+from datacontract.model.data_contract_specification import Contact, DeprecatedQuality, Field, Info, Model, Terms
 
 
 def info_breaking_changes(
@@ -216,8 +216,8 @@ def terms_breaking_changes(
 
 
 def quality_breaking_changes(
-    old_quality: Quality,
-    new_quality: Quality,
+    old_quality: DeprecatedQuality,
+    new_quality: DeprecatedQuality,
     new_path: str,
     include_severities: [Severity],
 ) -> list[BreakingChange]:

{datacontract_cli-0.10.15 → datacontract_cli-0.10.18}/datacontract/breaking/breaking_rules.py

@@ -42,6 +42,10 @@ class BreakingRules:
     field_primary_removed = Severity.WARNING
     field_primary_updated = Severity.WARNING
 
+    field_primary_key_added = Severity.WARNING
+    field_primary_key_removed = Severity.WARNING
+    field_primary_key_updated = Severity.WARNING
+
     field_references_added = Severity.WARNING
     field_references_removed = Severity.WARNING
     field_references_updated = Severity.WARNING