
 Usage: root export [OPTIONS] {FORMAT}

 Render each committed contract as `sql`, `jsonschema`, `avro`, `html` or `mermaid`.

 The engine (datacontract-cli) writes the format; this command picks the contracts and the
 files. A `status: proposed` contract is exported like any other. The dbt exports are not
 offered: `generate` owns the dbt keys. Each file written is an `info` diagnostic
 (`export/written`).

╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────╮
│ *    FORMAT      <str>  one of avro, html, jsonschema, mermaid, sql [required]                   │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
│ *  --out             <str>  directory to write <schema>/<table>.<ext> under [required]           │
│    --root            <str>                                                                       │
│    --relation        <str>  SCHEMA.TABLE to export; repeat it, or omit it for every contract     │
│    --dialect         <str>  SQL dialect for `sql` (auto, databricks, sqlserver, postgres, ...)   │
│                             [default: auto]                                                      │
│    --help                   Show this message and exit.                                          │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
