datacontract export great-expectations

Export a data contract to Great Expectations suite.

datacontract export great-expectations [OPTIONS] [LOCATION]

Argument	Default	Description
[LOCATION]	datacontract.yaml	The location (url, s3 url, or local path) of the data contract yaml.

Option	Default	Description
--engine	—	The engine used for Great Expectations run.
--dialect	auto	The SQL dialect. Use auto (default) to detect the SQL dialect via the specified servers in the data contract.
--output	—	File path where the exported data will be saved. If not provided, it will be printed to stdout.
--server	—	The server name to export.
--schema-name	all	Which schema to export, e.g., orders, or all for all schemas (default).
--json-schema	—	The location (url or path) of the ODCS JSON Schema.
--inline-references / --no-inline-references	--inline-references	Resolve authoritativeDefinitions of type definition, semantics or businessDefinition and inline them into the contract. Relative URLs and semantics IRIs are looked up on the ENTROPY_DATA_HOST (default https://api.entropy-data.com), other URLs are fetched directly, file references are read from disk. See https://cli.datacontract.com/semantics
--debug / --no-debug	—	Enable debug logging
--suite-name	—	The suite name for the Great Expectations run.
--checks	—	Comma-separated list of check categories to export (available: properties, quality). Omit to export everything.

datacontract export great-expectations datacontract.yaml --engine sql --dialect postgres --output expectations.json

Guide: Export: Great Expectations.