gt Is there a way to use more than one airbyte configuration

Question

gt Is there a way to use more than one airbyte configuration resource in one job So having two resource definitions but running them in one job consecutively with the run after argument So this is if I have two airbyte instances running

ben · Answer

Hi Konrad I believe there is a limitation about two separately configured resources with the same key in a single job you could use an asset sensor to have two jobs trigger sequentially to accomplish something similar

ben · Answer

We could provide the ability to change the asset key to avoid that collision issue That way you could have a set of assets pointed at one resource key and a set pointed at another Would that be useful for your use case

Konrad Schlatte · Answer

ok yes a sensor could be a solution can you point me to an example of a sensor that triggers a job when another job has successfully finished

ben · Answer

Hi Konrad I believe you can use a run status sensor <https docs dagster io apidocs schedules sensors dagster run status sensor>

ben · Answer

Here s an example of a simple one <https github com dagster io dagster blob ce7afb72e4a2f615eefa4de8e2fefa22c5da671d python modules dagster test dagster test toys run status sensors py L69|https github com dagster io dagster blob ce7afb72e4a2f615eefa4de8e2fefa22c5da671 on modules dagster test dagster test toys run status sensors py>

ben · Answer

Alternatively if you are using Assets an Asset Sensor might be a good choice <https docs dagster io concepts partitions schedules sensors asset sensors asset sensors 1>

Konrad Schlatte · Answer

ok thanks I just want to trigger an airbyte job when another airbyte job has finished so I suppose a run status sensor would make sense