Closed GtheSheep closed 1 year ago
Hey! Thanks for submitting, I also noticed this the other day but forgot to put an issue up 😅 haven't started working on it so a contribution would be very, very welcome!
This issue is stale because it has been open for 45 days with no activity.
This issue was closed because it has been inactive for 7 days since being marked as stale.
Hi! If that's ok and if you've not started working on it I might give a go at this feature.
Witht the circular dependency between Project > Jobs (require project id) and Job > Project source/freshness job (require job id), did you have an idea on how you'd like to handle those?
Would we create a new resource called
dbt_cloud_project_artifacts
(like in dbt Cloud), and 2 optional fields:freshness_job_id
documentation_job_id
Or would there be a way to handle that as part of the
dbt_cloud_project
resource directly?