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

dagster

i’m glad you are taking a look at the whole graphql schema

there is also graphene automagic that fails

```
class PipelineExecutionParams(graphene.InputObjectType):
    pipelineName = graphene.NonNull(graphene.String)
    config = graphene.Field(PipelineConfig)

    @staticmethod
    def validate(dict_):
        check.invariant(set(dict_.keys()) == set(['pipelineName', 'config']))
        return ExecutionParams(
            pipeline_name=check.str_elem(dict_, 'pipelineName'),
            config=dict_['config'],
        )
```

especially with these magic-laden libraries

it’s just like if i add another thing to PipelineExecutionParams and forget to add it to ExecutionParams

what is the state of your branch? I’ll be looking to start doing stuff fairly soon here.

I'll push today but I'm not sure it'll be runnable

I don't like how I have to mix graphql types and what would be model types

but it seems the only way that mkes sense in grapheen

creating instances of the Graphene classes is so odd

btw i would be in favor of having a naming convention