The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

You can use the configured() function/decorator to bind in default values

<@U018ELQ343U> Thanks for your answer, but I dont understand. Here is the pipeline decorator function: <https://docs.dagster.io/_apidocs/pipeline#pipeline-definitions> which attribute is responsible to setup this "partial run_config" ? can you please give me a very simple example, or point me to the documentation? thanks in advance

ok, I think I got it, <https://docs.dagster.io/_apidocs/modes-resources#modes> here I should explicitly give

<@U018ELQ343U> unfortunately I dont understand how should I do this, so please if you have time to send me an example, it would be appreciated thanks

I tried with this: <https://docs.dagster.io/0.9.2/overview/configuration/#configured> on the pipeline

since this is the `execution` section - you can use `configured` on the celery executor before you attach it to the mode definition

```pre_config_celery = configured(celery_executor)({...})
...
ModeDefinition(
 ...
  executor_defs=[pre_config_celery]
)```

aha....omg, i was not able to figure this out :wink:

Or in decorator form <https://github.com/geomagical/dagster-geomagical/blob/main/dagster_geomagical/executor.py>

yeah its a bit confusing so don’t feel bad

Same thing in the end, just different calling styles :slightly_smiling_face: