Currently, the dbt_cloud_job resource supports taking a deferring_job_id variable. In many cases, we would like to defer a job to a previous run of itself, which wouldn't be possible through using deferring_job_id as an argument when the job itself has not been created. It'd be great if the dbt_cloud_job resource support a defers_on_self boolean flag that would:
1) create the dbt_cloud_job resource
2) update the deferring_job_id field of the job to be its own ID
And the expected behavior is that the resource only expects either deferring_job_id or defers_on_self, with defers_on_self overriding deferring_job_id when set.
GtheSheep
commented
1 year ago
Currently, the
dbt_cloud_jobresource supports taking adeferring_job_idvariable. In many cases, we would like to defer a job to a previous run of itself, which wouldn't be possible through usingdeferring_job_idas an argument when the job itself has not been created. It'd be great if thedbt_cloud_jobresource support adefers_on_selfboolean flag that would: 1) create thedbt_cloud_jobresource 2) update thedeferring_job_idfield of the job to be its own IDAnd the expected behavior is that the resource only expects either
deferring_job_idordefers_on_self, withdefers_on_selfoverridingdeferring_job_idwhen set.