Hello Dagster team, Is it possible to “non_argument_deps” and “io_manager_key” for the asset at the same time? The motivation is that we want to trigger asset materialization when the upstream asset has materialized, but we don’t want to use/import upstream data to downstream asset. But we also want to update ‘another’ table in BQ. Using io_manager_key as a method of uploading the result on downstream asset would be ideal but not sure if having both params work as expected

hi @Wonjae Lee! that should work fine -- non_argument_deps just determines how the inputs should be loaded, and io_manager_key just determines how the output of the asset will be stored, so generally they don't interact

Thanks so much for the confirmation!