George Pearse
06/27/2022, 12:32 PM# the io manager stuff properly sorted.
# name of asset will be name of function definition
@asset(
required_resource_keys={"ml_mongo_warehouse"},
) # , non_argument_deps={'ml_cxr_datalake'})
def cxr_collection_metadata(context) -> pd.core.frame.DataFrame:
....
ml_cxr_collection_configured = with_resources(
[cxr_collection_metadata],
resource_defs={"ml_mongo_warehouse": mongo_handler_resource},
)
Bit perplexed, using very similar patterns successfully elsewhere. Problem resolves itself if I just bypass the dagster resource tooling, but that'd be a shame.chris
06/27/2022, 6:33 PMresource_config_by_key
argument of with_resources
, although if you need to change per run, that won't help you unfortunately.materialize
button - which I've created an issue for https://github.com/dagster-io/dagster/issues/8629. If you need to materialize runs with varying config, you can also just provide the assets to a job using define_assets_job
, and then use the launchpad for runs.