I'm a bit confused by why dagster can't resolve some dbt assets. I have:

@asset(
    key_prefix="prefix",
)
def some_asset(context, dbt_asset):

And this fails:

Input asset '["dbt_asset"]' for asset '["prefix", "some_asset"]' is not produced by any of the provided asset ops and is not one of the provided sources

But if I add an ins:

@asset(
    key_prefix="prefix",
    ins={"stock_group": AssetIn(key=["prefix", "dbt_asset"])},
)
def some_asset(context, dbt_asset):

Then everything works as expected. The asset key

["prefix", "some_asset"]

is being resolved by dagit for the GUI. Is there some limitation about what asset keys automatically can get resolved? (

some_asset

and

dbt_asset

are in different groups)

You need to use the explicit asset key as an “in” for your asset if the upstream asset has an asset key with multiple components. We’ve made this experience more streamlined in our latest APIs: https://github.com/dagster-io/dagster/discussions/14964