👋 This week's release of

dagster-dbt

(0.19.12) introduces experimental APIs to improve the ergonomics of defining python dependencies upstream and downstream of dbt assets. This discussion details the new APIs, please comment with any feedback or questions! The new methods are utilities to fetch asset keys from the dbt manifest, intended to be used with

@asset(key=...)

to define python dependencies. A brief summary: • `DbtManifest.get_asset_key_for_source`: fetches the asset key of a dbt source • `DbtManifest.get_asset_key_for_model`: fetches the asset key of a dbt model

Hi, nice feature ! One question : as I see a manifest path input, is this possible with

load_asset_from_dbt_project

?

Hi @Malo PARIS! Do you mind asking your question in the GitHub discussion for broader visibility?