hello all! I'm wondering if there's a way to trigger a dagster job to run from another dagster job. a bit of context: I want to have different k8s resources for these two jobs. one of them will have a volume mounted with secrets that i don't want the other job exposed to.

One way that we’ve seen folks set up cross-job dependencies is to use asset sensors: https://docs.dagster.io/concepts/partitions-schedules-sensors/sensors#asset-sensors Often these cross-job dependencies have some tangible data asset that is implicitly handed off. You can model that with an asset materialization in the first job, and connect the second job to an asset sensor listening for new materializations of that asset.