Adds the basic interface for a RunLauncher to be loaded by an instance and available via GraphQL.
my only question is here the relationship between "enqueued" and "startScheduled" execution. what if you want to have the "StartScheduled" one actually enqueue
I actually think enqueueing should probably be the default behavior?
ya thats a good question Im not sure the right answer to, seems like the options are:
- bool flag on startScheduled or moral equivalent
- startScheduled uses run_queue if its present otherwise starts directly
- remove execution_manager in dagster-graphql to run_queue and remove the distinction between start and enqueue from the whole system