This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Releases: PrefectHQ/prefect-dbt
Releases · PrefectHQ/prefect-dbt
v0.4.1
What's Changed
- Bump actions/checkout from 3 to 4 by @dependabot in #157
- 'Update the pin on
prefect
version' by @urimandujano in #160 - Bumps build's python version by @urimandujano in #161
New Contributors
- @urimandujano made their first contribution in #160
Full Changelog: v0.4.0...v0.4.1
v0.4.0
What's Changed
- Update DbtCoreOperation docstring for docs fix by @robfreedy in #143
- corrected typo in code snippet by @Bada-S in #149
- Update Code Owners by @jawnsy in #151
- Fix typo by @seanpwlms in #141
- Fixes example for saving a
DbtCloudJob
block by @desertaxle in #156 - Conditional imports to support operating with
pydantic>2
installed by @chrisguidry in #159
New Contributors
- @robfreedy made their first contribution in #143
- @Bada-S made their first contribution in #149
- @jawnsy made their first contribution in #151
- @seanpwlms made their first contribution in #141
- @chrisguidry made their first contribution in #159
Full Changelog: v0.3.1...v0.4.0
v0.3.1
v0.3.0
0.3.0
Released on February 16th, 2023.
Breaking: BigQueryTargetConfigs.get_configs
is no longer synchronous and the input type of GlobalConfigs.log_format
is now string.
Added
DbtCloudJob
block andrun_dbt_cloud_job
flow - #101DbtCoreOperation
block - #119SqlAlchemyConnector
support for use forPostgresTargetConfigs
- #123
Changed
- The minimum version of
prefect-snowflake
- #112 - Decoupled fields of blocks from external Collections from the created dbt profile - #112
DbtCliProfile
is now accepts aUnion
ofSnowflakeTargetConfigs
,BigQueryTargetConfigs
, andPostgresTargetConfigs
for creation on UI - #115- Breaking: Made
BigQueryTargetConfigs.get_configs
synchronous - #120 dbt_core
is now included in the requirements - #119
Deprecated
DatabaseCredentials
used inPostgresTargetConfigs
in favor ofSqlAlchemyConnector
- #123
Fixed
v0.2.7
v0.2.6
v0.2.5
v0.2.4
0.2.4
Released on October 26th, 2022.
This release introduces the ability to selectively retry failed steps in a dbt Cloud job run. dbt Cloud jobs triggered by Prefect can now be more resilient to the transient failures such as:
- Connection timeouts with a database
- Another dbt job is interacting with the same table as the current job and causing concurrency issues at the database level
Huge thanks to @dpguthrie and @sungchun12 for their help developing this new functionality!
Added
retry_dbt_cloud_job_run_subset_and_wait_for_completion
flow andretry_*
keywords intrigger_dbt_cloud_job_run_and_wait_for_completion
flow - #89get_dbt_cloud_job_info
task #89
Changed
- Allow registering all blocks at top level - #79
v0.2.3
0.2.3
Released on October 4th, 2022.
Added
- Support
Oauth Token-Based
inBigQueryTargetConfigs
- #68