Hi! Is there a way to provide

run_config

for

build_asset_reconciliation_sensor()

somehow?

Hi Mykola - can you explain your use case a little more? Why are you using config in this situation?

I have some resources used by assets. So to materialize them I need the resources to be configured. They are configured pretty well in case of materialization by a

job

but there is no place to configure them in case of reconciliation sensor. Or did I miss something?

Got it - our recommended way of configuring resources in this situation is with

configured

. For example:

defs = Definitions(assets=..., resources={"my_resource_key": my_resource.configured(...)})

More detail here: https://docs.dagster.io/concepts/configuration/configured#using-configured

@sandy, our use is mostly related to sensitive parameters (e.g. db connection credentials). For the moment we use env variables passed as StringSource fields in config (as this was a recommended way). About hardcoding the behavior: that may work for our own resource definitions, but standard Dagster resources (like "s3_resource") should not be changed probably.

configured

is an option here. Will it work for assets as well?

configured

works for resources, but not for assets. when I asked if you could just hardcode the behavior inside the function body, I only meant to suggest that for assets, not for resources