sodadata / soda-sql

Soda SQL and Soda Spark have been deprecated and replaced by Soda Core. docs.soda.io/soda-core/overview.html
https://docs.soda.io/
Apache License 2.0
61 stars 17 forks source link

Allow for soda ingest to get runs from a job id rather than expecting run ids on CLI #190

Closed bastienboutonnet closed 2 years ago

bastienboutonnet commented 2 years ago

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-runs

We should think about first querying that information and then downloading the latest run's (or anything else that makes sense) artifacts.