Hi all, new dagster user here. We are trying to orchestrate Airbyte with Dagster and noticed that terminating a Job via the Dagster UI does not trigger the Airbyte API. As a result, the Airbyte Connection keeps syncing instead of being cancelled. It seems that this functionality is not implemented in the

AirbyteResource

class. Does anyone know if there is a workaround for this? Or if there exists some kind of hook in the dagster source code so that we could implement this ourselves? Thanks a lot in advance for your support.

cc @owen

hi @Timo Hartmann! great question, and another user actually just mentioned this as well. I'll see if I can get a fix in for next week's release. I created an issue tracking this here: https://github.com/dagster-io/dagster/issues/7630.

Hi @owen, thanks a lot for the quick response. Looking forward to seeing this implemented 🙂