Hi everyone I understand that it s possible to parametrize `

Question

Hi everyone I understand that it s possible to parametrize `asset`s using `config schema`s However I m not quite sure how I can supply these config values to `asset`s in a scheduled or reactive setting A minimal code example is provided in the thread Thanks in advance raised hands

Christopher Tee · Answer

Minimal code example ``` asset config schema= input a str def a asset config schema= input b bool def b a Make `asset a` run on a schedule update job = define asset job name= update job selection=AssetSelection keys a update job schedule = ScheduleDefinition name= update job schedule job=update job cron schedule= Make `asset b` automatically materialize after `asset a` update sensor = build asset reconciliation sensor name= update sensor asset selection=AssetSelection all defs = Definitions assets= a b schedules= update job schedule sensors= update sensor ```

Zach · Answer

you can use the `config` parameter of `define asset job` to make configured versions of your asset job and then schedule those something like ```update job = define asset job name= update job selection=AssetSelection keys a config= ops b config input a True update job schedule = ScheduleDefinition name= update job schedule job=update job cron schedule= ```

Christopher Tee · Answer

Thanks < Zach> for the response I tried your solution and it seems that you can only specify the config corresponding to the selected asset in `define asset job` So in the example above I can only provide config values for Asset `a` ```update job = define asset job name= update job selection=AssetSelection keys a config= ops a config input a hello ``` Providing config values for Asset `b` leads to an error on `dagster dev` initialization since it s not part of the selected assets ```dagster daemon SchedulerDaemon WARNING Could not load location scheduling py to check for schedules due to the following error dagster core errors DagsterInvalidConfigError Invalid default value for Field Error 1 Received unexpected config entry b at the root Expected a config input a String outputs result json path String pickle path String ``` By specifying config values for Asset `a` only Dagster can be initialized but later fails when the schedule amp sensor are activated ```ERROR Sensor daemon caught an error for sensor update sensor Traceback most recent call last File python3 10 site packages dagster daemon sensor py line 489 in process tick generator yield from evaluate sensor File python3 10 site packages dagster daemon sensor py line 653 in evaluate sensor run = get or create sensor run File python3 10 site packages dagster daemon sensor py line 780 in get or create sensor run return create sensor run File python3 10 site packages dagster daemon sensor py line 815 in create sensor run external execution plan = repo location get external execution plan File python3 10 site packages dagster core host representation repository location py line 750 in get external execution plan execution plan snapshot or error = sync get external execution plan grpc File python3 10 site packages dagster api snapshot execution plan py line 65 in sync get external execution plan grpc raise DagsterUserCodeProcessError from error info result error dagster core errors DagsterUserCodeProcessError dagster core errors DagsterInvalidConfigError Error in config for job Error 1 Missing required config entry ops at the root Sample config for missing entry ops a config input a b config input b True ``` So the remaining question is how to configure the config values for asset `b` materialized by automatic reconciliation I m guessing it involves supplying configs to a `RunRequest` in a ` sensor` The issue is that this sensor is a reconciliation sensor and there s no way I m aware of to provide config values to `build asset reconciliation sensor`