Use a script to kick off a pipeline run.
Are we exposing or documenting stuff under dagster.core.host_representation like ManagedGrpcPythonEnvRepositoryLocationOrigin, LoadableTargetOrigin, and PipelineSelector, which have been mentioned in this example?
Should we? Without linking to detailed API docs or further explanation, it could be a bit hard for users to digest what's going on when using these suggested APIs. cc @dgibson: as you may have more context in this corner of the codebase.
Besides, I dont think we have documented any of the dagster-graphql apis? Shall we start documenting dagster-graphql? - AFAIK we've been treating it as more of an internal-only package
plz rebase master and make sure you've picked up the latest changes. i think this has been addressed in D5824
Yeah, this is fine in that it works but this is not the right way to run a pipeline over GraphQL. The right way to run a pipeline over graphql is to start a dagit server and to query the server.