oliver-twist
DAG Auditor
oliver-twist is a dag auditing tool that audits the DBT DAG and generates a summary report. There is a docs site, including descriptions of all currently implemented rules.
Getting Started
To get started, install the package
$ pip install olivertwist
and then run it by passing it your dbt manifest JSON
olivertwist check manifest.json
This will report any failures to the console, and also in HTML format in a directory called target. You can optionally auto-open the report in a browser with:
olivertwist check manifest.json --browser
Full options are available with:
olivertwist check --help
Configuration
All rules are enabled by default. To change this you need a configuration file called olivertwist.yml in the same directory you are running olivertwist. An example configuration is shown below:
version: '1.0'
universal:
- id: no-rejoin-models
enabled: false
- id: no-disabled-models
enabled: true
There is a command to help you generate the config automatically:
olivertwist config
This will show all the available rules and allow you to toggle the ones that you want to enforce.
Local Development
Clone this repo and install the project:
poetry install
Install pre-commit hooks for linting
This is optional, but highly recommended to avoid annoying linting failure in CI.
poetry run pre-commit install
To run the pre-commit hooks locally:
poetry run pre-commit run
To get the latest versions of the dependencies and to update the poetry.lock file run:
poetry update
To run oliver-twist and generate the summary report run:
poetry run olivertwist example_manifest.json
Working with diagrams
To update and regenerate the images that illustrate rule failures in the documentation follow the next steps:
- update the diagrams using the mermaid syntax
- install yarn
cd docs/diagrams./generate.sh- inspect the generated images in
./docs/diagrams/output/ - if you're happy with the results, run
./copy.shso that they are copied over to./docs/images - you can now reference those images. e.g. in
.docs/rules.md
Creating a distribution
poetry build --format wheel
Metadata
Release files for olivertwist 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| olivertwist-0.2.tar.gz | 1.4 MB | Without provenance | Details for olivertwist-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| olivertwist-0.2-py3-none-any.whl | Python 3 | none | any | Details for olivertwist-0.2-py3-none-any.whl |
Total release size: 2.8 MB
Release files / olivertwist-0.2.tar.gz
| Download URL | olivertwist-0.2.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
648d6b023d024cb619daa92c6734f3885e32ed6b889dedc40e55cc1ad664d910
|
|
BLAKE2b-256 checksum How to use checksums |
d44a1b5d1caa7ee57f1dccf5f32fea5d46e59bbf33c14cea731a0273fdefa8f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.8.0 Darwin/19.6.0
|
Release files / olivertwist-0.2-py3-none-any.whl
| Download URL | olivertwist-0.2-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00a4b27d624e609f0abd207af294a824375dc07a5cff5451c7a7e916c3e52052
|
|
BLAKE2b-256 checksum How to use checksums |
69440459bca3eb67f4032cec642bb10c06d12bda0c0355c390983e265ba86c31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.8.0 Darwin/19.6.0
|
Security for olivertwist 0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.