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

dagster

In `run_status_sensor` is there a reason the `monitored_jobs` argument accepts a `JobSelector` type, but `request_job` needs a `JobDefinition`type? Using `JobSelector` allows us to layout our code more logically without having to import from multiple levels. Is it possible to use `JobSelector` inside of the sensor definition and pass that to the `RunRequest`?

Able to get around this using an `UnresolvedAssetJobDefinition`