The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Crossposting from <#C01U5LFUZJS|dagster-feedback>! There are new experimental APIs in `dagster-dbt` for creating software-defined assets from your dbt projects in a more ergonomic and composable way, and we’d love your feedback on our current direction :slightly_smiling_face:

We intend for these APIs to be a replacement to the current APIs of:
• `load_assets_from_dbt_manifest` (<https://github.com/dagster-io/dagster/blob/release-1.3.6/python_modules/libraries/dagster-dbt/dagster_dbt/asset_defs.py#L549-L636|link>)
• `load_assets_from_dbt_project` (<https://github.com/dagster-io/dagster/blob/release-1.3.6/python_modules/libraries/dagster-dbt/dagster_dbt/asset_defs.py#L421-L511|link>)
• `DbtCliClient` (<https://github.com/dagster-io/dagster/blob/release-1.3.6/python_modules/libraries/dagster-dbt/dagster_dbt/cli/resources.py#L127-L137|link>)
<https://dagster.slack.com/archives/C01U5LFUZJS/p1685051713480429>

see <https://github.com/dagster-io/dagster/discussions/14477#discussioncomment-6031833> for maybe better visibility of my questions to the new API

plus: <https://github.com/dagster-io/dagster/discussions/14477#discussioncomment-6031852>

Will these new apis make it easier to set up schedule-less refreshes using source observable assets and auto materialization?

Refining my question, will the @dbt_assets decorator be getting, similar to the @asset decorator, the ability to set an auto_materialize_policy and freshness_policy?

Hey <@U04660NCVRT>, mind asking your question in the RFC for broader visibility? I can answer it there!