Heya folks, Is there a way to introduce a dependency between assets that are already created. eg. I’m using dagster-fivetran and dagster-dbt to generate assets since these both produce assets themselves you don’t really bear a lot of control on the dependency. how can i introduce a dependency between these two groups of assets ?

@yuhan I’m not sure this works when the assets are loaded via dbt and fivetran packages, because you aren’t explicitly defining the assets. They just get loaded. I am trying to do something similar, and have the following code to run it:

@asset(required_resource_keys={"dbt"}, name='force_dbt_run_job',
ins={"upstream": AssetIn(key="dim_products")},
non_argument_deps={"force_update_dim_products"})
def force_updated_job(upstream):
    return upstream

I am trying to return the “dim_products” asset and re-materialize it (I need to do some manual manipulation of the data) but I don’t know of a graceful way to do that….this code doesn’t work because it looked in local storage for the asset, rather than wherever dbt is storing it.

@Bojan if you haven't solved it hope this helps: https://dagster.slack.com/archives/C04CW71AGBW/p1674273469174249

Thanks that’s very helpful i’ve however been experiencing other issues with fivetran as of yesterday with the build fivetran asset function. https://dagster.slack.com/archives/C047VPGQUTV/p1674732399820039