hey folks, is there a way to include an IO manager in a materialize call even if it is unused by the assets being materialized? I'm dynamically populating a list of assets to materialize (based on user input) and would like to avoid having to check if a particular asset is present to decide whether to include the corresponding IO manager in the run_config. Is there a way to just include the IO manager in the run config regardless of whether it is used?

yeah you should be able to do that. Dagster doesn’t do any checks to ensure that all resources in the run config are used by the assets being materialized

how would I do that? including it in the run config results in an error related to an unexpected key in the run configuration (unless i include the asset that uses it in the materialize call)

oh ok i might be mistaken