Users on dbt Cloud will typically schedule "Jobs". Those jobs trigger "Runs" and we want to ingest the results from runs. However, since this is automated, we can imagine that users of soda will not want to go and manually feed the --dbt-cloud-run-id since they won't be the ones running the jobs.
Users on dbt Cloud will typically schedule "Jobs". Those jobs trigger "Runs" and we want to ingest the results from runs. However, since this is automated, we can imagine that users of soda will not want to go and manually feed the
--dbt-cloud-run-id
since they won't be the ones running the jobs.The admin API can return a list of runs given a
job_id
: https://docs.getdbt.com/dbt-cloud/api-v4#operation/list-account-runsWe should think about first querying that information and then downloading the latest run's (or anything else that makes sense) artifacts.