- Group Reviewers
- R1:021cc034dea5: Create Scheduler GraphQL interface
this seems accidental?
actually i would consider just adding file_path as a property to RunSchedule that doesnt get exposed to graphql
I think it might be best to leave it to the Scheduler implementation, since other implementations won't won't need file paths, will need to store multiple file paths, or use a database, etc.
For ex: I'll need to add a path to the cron shell script for this scheduler.
is String right here? we just send the json blob?
maybe use a string instead of 1? not sure how beneficial it actually is, depends where the value actually shows up
might be worth having a slightly different name since this returns a string that needs to get json decoded by the client
I think so. I don't see a situation where you would want to get just a part of the execution params, and I don't see a way to make it query-able since the structure changes based on config.