Releases: dpguthrie/dbtc
Releases · dpguthrie/dbtc
v0.2.1
v0.2.0
[0.2.0] - 2022-08-30
Added
- The ability to restart a job from failure. The
trigger_job
method now accepts an argumentrestart_from_failure
(defaultFalse
) that will determine whether or not the last run attempt for a job was unsuccessful - in the event it was, it will parse the steps within that job and find the nodes that it needs to rerun as well as any steps that were skipped entirely. - Additional commands to the
trigger_job
method:should_poll
- Indicate whether or not the method should poll for completion (defaultTrue
)poll_interval
- How long in between polling requests (default 10 seconds)restart_from_failure
- Described abovetrigger_on_failure_only
- Only relevant when settingrestart_from_failure
toTrue
. This has the effect, when set toTrue
, of only triggering the job when the prior invocation was not successful. Otherwise, the function will exit prior to triggering the job (defaultFalse
)
- Logging to stderr when using the
trigger_job
method (internally using therich
package that comes when installingTyper
) - Multiple tests for the
restart_from_failure
functionality
Removed
- The
trigger_job_and_poll
method within thecloud
property of thedbtCloudClient
class. The polling functionality is now rolled up into the singletrigger_job
method with the argumentshould_poll
(default isTrue
)
v0.1.4
v0.1.3
v0.1.2
Fixed
- The
_dbt_cloud_request
private method, which is used in the CLI, now only usestyper.echo
to return data from a request.
Changed
- The
trigger_job_and_poll
method now returns theRun
, represented as adict
. It will no longer raise an exception if the result of the run is cancelled or error.