Releases: dpguthrie/dbtc
Releases · dpguthrie/dbtc
v0.11.5
[0.11.5]
Added
- New
search
method in the metadata client for searching across dbt resources - Retry logic to the common session object for the following status codes: 429, 500, 502, 503, 504
Updated
public_models
method on themetadata
property - now allows for argument-based filtering.
Removed
- Rudderstack tracking code
Full Changelog: 0.11.4...0.11.5
v0.11.4
v0.11.3
v0.11.2
v0.11.1
Fix versioning
Full Changelog: 0.11.0...0.11.1
v0.11.0
What's Changed
- CLI Command Groups, new metadata methods by @dpguthrie in #102
Full Changelog: 0.10.0...0.11.0
v0.10.0
v0.9.0
[0.9.0] - 2024-01-11
Removed
- All of the methods in the
_MetadataClient
(dbtCloudClient.metadata
) except forquery
. The Discovery API no longer allows a user to specify every single field recursively, which is what thesgqlc
package would do.
Added
- An optional keyword argument
use_beta_endpoint
to thedbtCloudClient
class. This will default toTrue
, which means that the Discovery API will use the beta endpoint at https://metadata./beta/graphql instead of https://metadata./graphql. This contains both the stable API resources (environment, models, tests, etc.) but also contains things for performance, recommendations, and lineage. - Ability to automatically paginate requests for the Discovery API. If pagination is required/desired, ensure that your query is properly created with an
$after
variable and all of the fields within thepageInfo
field.
Updated
- Loosen restrictions on Pydantic - ">=2.0,<3.0"
v0.8.0
[0.8.0] - 2023-12-04
Added
retries
argument to thetrigger_job
method. This will allow you to retry a jobretries
amount of times until completion, which is defined assuccess
orcancelled
.
Updated
trigger_job_from_failure
method to point at the newrerun
endpoint. Logic is no longer necessary internally.