Is there way to define phantom assets other than using

SourceAsset

? We are using Databricks and Delta Lake engine so we do not need actual IO Managers for assets materializations but want to maintain declarative assets catalog with dependencies. Is there way to just declare assets definitions and dependencies between them, but all actual materializations will be handled by jobs (and not

@assets

methods) spawning materializations events upon completion.

@op(
    ins={"...": In(asset_key=AssetKey(["..", ".."]))},
    out=Out(io_manager_key="...", asset_key=AssetKey(["..", ".."])),
)

This works mostly without @asset . You can still see that there will be an asset but the graph and most info only appear after a run. Also materialize does not work. I don’t think it works for Dynamic outputs.

Hey Ivan - a couple additional points here: • You don't need to use IO managers to use assets. E.g. you can write assets where the body of the decorated function does the IO, like in the examples here: https://docs.dagster.io/concepts/assets/software-defined-assets#non-argument-dependencies. • In 0.15.0, we released a new way of interleaving ops with assets: https://docs.dagster.io/concepts/assets/software-defined-assets#graph-backed-assets.