DBT extension for Metaflow
This extension adds support for executing DBT models as part of steps in Metaflow Flows via decorators.
Basic usage
Having a dbt_project.yml as part of your Flow project will allow executing dbt run as a pre-step to any task by simply adding the decorator to a step.
@dbt
@step
def start(self):
# DBT Models have been run when step execution starts
self.next(self.second_step)
If you only want to run a specific model as part of a step, you can specify this with the models= attribute
@dbt(models="customers")
Configuration options
Project directory
You might want to keep the DBT project separately nested within the Flow project. In these cases you would need to specify the location of the DBT project folder, due to the way project lookup works. This can be done by specifying the project location as a relative or absolute path within the decorator
@dbt(models="customers", project_dir="./dbt_project")
Supplying credentials
When deploying a DBT flow to be executed remotely, we do not want to bundle up sensitive credentials into the code package. Therefore a plain text profiles.yml will not suffice.
We can utilize the environment variable replacement that DBT offers to get around this.
example profiles:
dbt_decorator:
outputs:
dev:
type: postgres
threads: 1
host: localhost
port: 5432
user: "{{ env_var('DBT_POSTGRES_USER') }}"
pass: "{{ env_var('DBT_POSTGRES_PW') }}"
dbname: dbt_decorator
schema: dev_jaffle_schema
prod:
type: postgres
threads: 1
host: localhost
port: 5432
user: "{{ env_var('DBT_POSTGRES_USER') }}"
pass: "{{ env_var('DBT_POSTGRES_PW') }}"
dbname: dbt_decorator
schema: prod_jaffle_schema
target: dev
Note: any profiles.yml in the flow project folder will be packaged, so make sure that they do not contain sensitive secrets.
We can supply the environment variables in various ways, for example
- having them already present in the execution environment
- supplying them with the
@environmentdecorator in the flow (this still ends up bundling secrets into the package, but is good for testing) - hydrating environment variables with the
@secretsdecorator from a secret manager.
Examples
The command metaflow dbt examples will pull example flows to your working directory under metaflow-dbt-examples.
Follow the README.md under the examples directory for more instructions.
Metadata
Release files for metaflow-dbt 1.0.7
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 | |
|---|---|---|---|---|
| metaflow_dbt-1.0.7.tar.gz | 97.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| metaflow_dbt-1.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 210.5 kB
Release files / metaflow_dbt-1.0.7.tar.gz
| Download URL | metaflow_dbt-1.0.7.tar.gz |
|---|---|
| Size | 97.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b8e1fd2025095cea99465da7215f4d86658032faabe8da30ad79923eb876ebd
|
|
BLAKE2b-256 checksum How to use checksums |
27d7df67ddc2f8b2f19d0152e6fe68f32425ecbb07b88c4822d7a37ed1980aaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Dec 19, 2024.
Transparency logRelease files / metaflow_dbt-1.0.7-py3-none-any.whl
| Download URL | metaflow_dbt-1.0.7-py3-none-any.whl |
|---|---|
| Size | 113.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5d6326080ff5aff4788758c2bc4856a5d00654c68f194a7cf4f8ab83f1213e6
|
|
BLAKE2b-256 checksum How to use checksums |
180d2fea0aa00e95b115c3839f8a1839a3ecae86c29e45252ec58068082a8583
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Dec 19, 2024.
Transparency logSecurity for metaflow-dbt 1.0.7
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for metaflow_dbt-1.0.7.tar.gz
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 Dec 19, 2024.
Transparency logA 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.