Hi team! I am currently using the

load_assets_from_dbt_manifest

to load all my assets once and then declare multiple

DbtManifestAssetSelection

to select dbt models that I want to run in dagster jobs. If I switch to

@dbt_assets

, can I continue using

DbtManifestAssetSelection

to create asset selections of my dbt assets, or should I take a different approach altogether? This is an example of my current configuration:

dbt_assets = load_assets_from_dbt_manifest(
    manifest_file,
    io_manager_key="io_manager",
    key_prefix=["analytics"],
    source_key_prefix=["analytics"],
    node_info_to_group_fn=node_info_to_group_fn,
)

antifraud_dbt_assets = DbtManifestAssetSelection(
    manifest_json=manifest_file,
    select="tag:antifraud",
    node_info_to_asset_key=node_info_to_asset_key,
)

antifraud_assets_job = define_asset_job(
    name="antifraud_assets_job",
    executor_def=in_process_executor,
    selection=antifraud_dbt_assets,
)

I then declare

antifraud_assets_job

in my repository.

Look at the recent changes to the dbt cli client in this discussion

Hi @Dennis Gera! Sorry, I’ve seen your reply to the discussion, but I haven’t gotten around to answering — hoping to get an answer to you later today

Hi @rex, thanks!