dre-cli
DRE, the Declarative Reporting Engine, is open-source reports as code. You keep each report
as .sql and YAML files in git; DRE runs the SQL against your databases (each tab of a workbook can
come from a different one, and tables can be declared as dbt-style sources), writes the result as
csv, delimited, fixed-width, parquet or xlsx (including multi-sheet workbooks, number formats,
formulas and totals rows, and branded Excel templates), and delivers the file wherever it needs
to go: email, SFTP/FTP, S3, GCS, Azure Blob, Databricks Volumes or Slack. A report can also send a
headline message built from its results, to Slack or email (Microsoft Teams and
Google Chat are in preview). It runs on whatever scheduler you already have: cron, Airflow, Dagster, Databricks Jobs.
If you know dbt, you already know DRE: a project of SQL and YAML, Jinja and macros, ref(),
source(), folder config, tags, selectors, profiles and targets. dbt builds your tables; DRE
delivers the last mile, the reports people receive. DRE is inspired by dbt and is an independent
project, not affiliated with or endorsed by dbt Labs, Inc. (dbt is their trademark).
DRE and dbt, side by side.
pip install dre-cli # or: uv tool install dre-cli
dre --help
This package holds the dre 0.4.4 executable. Plugins (databases, file formats,
destinations) are installed by dre on demand, for the ones a project declares. From Python:
dre_cli.run(["run", "-s", "daily"]).
In a Databricks job, add dre-cli to the job's environment dependencies and run dre (or
python -m dre_cli) from a script or notebook.
Documentation: getdre.com/docs. Source and issues: github.com/get-dre/dre.
1 maintainer
Metadata
1 maintainer
Release files for dre-cli 0.4.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| dre_cli-0.4.4-py3-none-win_arm64.whl | Python 3 | none | Windows ARM64 | Details |
| dre_cli-0.4.4-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| dre_cli-0.4.4-py3-none-manylinux_2_35_x86_64.whl | Python 3 | none | Linux glibc 2.35+ x86-64 | Details |
| dre_cli-0.4.4-py3-none-manylinux_2_35_aarch64.whl | Python 3 | none | Linux glibc 2.35+ ARM64 | Details |
| dre_cli-0.4.4-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| dre_cli-0.4.4-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 60.2 MB
Release files / dre_cli-0.4.4-py3-none-win_arm64.whl
| Download URL | dre_cli-0.4.4-py3-none-win_arm64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | Python 3 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
eb9bad28d06469cfa873e5060adb62fb28efe1fbfa2c8c52b2c0491a75858dff
|
|
BLAKE2b-256 checksum How to use checksums |
66e21e638f3c674fb51e6bf154c82fd4a14fe56b84bc6c48f785c724d55b7bd2
|
| 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 Oct 15, 2026.
Transparency logRelease files / dre_cli-0.4.4-py3-none-win_amd64.whl
| Download URL | dre_cli-0.4.4-py3-none-win_amd64.whl |
|---|---|
| Size | 9.6 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0f4aee06850ed109ad7d16d06e393e222d3d5001a11f18b095883e398d428f80
|
|
BLAKE2b-256 checksum How to use checksums |
573aee36d4311c306e7fb0c74cff00a6b15d246176216eecc229d648a849b5f7
|
| 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 Oct 15, 2026.
Transparency logRelease files / dre_cli-0.4.4-py3-none-manylinux_2_35_x86_64.whl
| Download URL | dre_cli-0.4.4-py3-none-manylinux_2_35_x86_64.whl |
|---|---|
| Size | 11.1 MB |
| Tags | Linux glibc 2.35+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
fa6d01645e4b58e65584916397df8e2a5b5376b096f2dcc15f700942301d2f78
|
|
BLAKE2b-256 checksum How to use checksums |
be6f0e1d65c481a08992de598a53ae300f11011b567e28fad279070330442675
|
| 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 Oct 15, 2026.
Transparency logRelease files / dre_cli-0.4.4-py3-none-manylinux_2_35_aarch64.whl
| Download URL | dre_cli-0.4.4-py3-none-manylinux_2_35_aarch64.whl |
|---|---|
| Size | 10.8 MB |
| Tags | Linux glibc 2.35+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
b8e9c1944c3ab41f9301e94d073c170b53068ee75ca5698f57a896ad323e936b
|
|
BLAKE2b-256 checksum How to use checksums |
b460024f6cff158f6a947462e79c817b44f402997e59bb78d76ebee7bd36520e
|
| 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 Oct 15, 2026.
Transparency logRelease files / dre_cli-0.4.4-py3-none-macosx_11_0_arm64.whl
| Download URL | dre_cli-0.4.4-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 9.8 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
39c55e7e5692940f4b362dfee4d79abc8374fd36c11c19b9d2810e92e0024a43
|
|
BLAKE2b-256 checksum How to use checksums |
1c31b6ac1547c29137666fba677cd831058bedcee044afcbc367e0906a95680c
|
| 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 Oct 15, 2026.
Transparency logRelease files / dre_cli-0.4.4-py3-none-macosx_10_12_x86_64.whl
| Download URL | dre_cli-0.4.4-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
a54e56f31e86f20609700210891137fb8bbc9137bdc6b461613fb919b8bf0f6c
|
|
BLAKE2b-256 checksum How to use checksums |
92761f12901adff0245c841e568b3ec3ce3a87494112c43cb024b53eae4f2286
|
| 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 Oct 15, 2026.
Transparency log
