Closed dannyroosevelt closed 1 year ago
I'm working on this right now! Not my top priority, but I'm slowly chipping away at it.
Actions that I'm working on (in that order):
manifest.json
, run_results.json
or catalog.json
)DBT Cloud also supports webhooks for completed or failed jobs, which could be a useful trigger.
There's no way to tie a webhook directly to a specific run/workflow (we can only configure a static callback URL), but in theory it should be possible to use the trigger to resume a paused workflow if the resume URL for that workflow is kept in a data store (the connection could be established via the run ID).
Hi everyone, all test cases are passed! Ready for release!
Test report https://vunguyenhung.notion.site/Components-dbt-Cloud-7262-f8644a18f4b84381bc97accf5b5ce507
Thanks - works great!
App
dbt Cloud https://www.getdbt.com/
Triggers:
Actions:
Jobs: Trigger Job Run (also with the option to retrieve the run once completed) https://docs.getdbt.com/dbt-cloud/api-v2#/operations/Trigger%20Job%20Run
Runs: Retrieve Run https://docs.getdbt.com/dbt-cloud/api-v2#/operations/Retrieve%20Run
Environments: Retrieve Environment https://docs.getdbt.com/dbt-cloud/api-v2#/operations/Retrieve%20Environment
Runs: Retrieve Run Artifact https://docs.getdbt.com/dbt-cloud/api-v2#/operations/Retrieve%20Run%20Artifact