Think this is a dagster error? Not being provided ...
# ask-community
g
Think this is a dagster error? Not being provided an option to specify config yaml via the UI, and receive this error for this configured asset below.
Copy code
# 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:
    ....
Copy code
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.
c
A quick fix could be to provide the config using the
resource_config_by_key
argument of
with_resources
, although if you need to change per run, that won't help you unfortunately.
I think the issue here is the lack of a yaml editor showing up when kicking off runs using the
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.
👍 1