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

dagster

example.py

Trying to understand what should be passed into the run_config based upon the error trace
```dagster/lib/python3.9/site-packages/dagster/core/system_config/objects.py", line 160, in build
    raise DagsterInvalidConfigError(
dagster.core.errors.DagsterInvalidConfigError: Error in config for job
    Error 1: Missing required config entry "inputs" at the root. Sample config for missing entry: {'inputs': {'number': '&lt;selector&gt;'}}```

Found a way to do so but it doesn't seem that robust
```to_fahrenheit.to_job(input_values={"number": 789}).execute_in_process(
        run_config=run_config
    )```

I think you can use something like
```run_config = {
        "ops": {"config": {"from_unit": "kelvin"}},
        "inputs": {"number": {"value": 789}}
    }```
I wish I could point you to a doc but I haven't seen much that shows how to configure a graph input that doesn't come from another graph. the closest I can find is <https://docs.dagster.io/concepts/ops-jobs-graphs/nesting-graphs#sub-graph-inputs-and-outputs|sub-graphs> - I think the point is that usually the `number` parameter would be passed by another graph or op, liked in the example on <https://docs.dagster.io/concepts/ops-jobs-graphs/nesting-graphs#nesting|graph nesting>

Thanks <@U0300665S8G> for the explanation.
Got the entire DAG working