Hi Jaikant, I could imagine a PipelineDefinition that’s created from a yaml file - the only requirement that dagster has is that you can call a function to construct your repository that specifies a PipelineDefinition for each of your pipelines. Most often each pipeline definition is static and created in code, but as long as a PipelineDefinition is returned when that function is called, the system should be fine.
Constructing a pipeline definition via graphql isn’t something that we have any support for currently though.