Dbtc

Fixed

- The list_environments method and CLI invocations

Fixed

- Versioning issue

Added

- New command line groups (e.g. instead of `dbtc list-accounts`, you would use `dbtc accounts list`). Older methods are still around but will be deprecated in future versions.
- New discovery API convenience methods to retrieve performance, recommendations, and other information

Added

- Semantic layer client. This can be accessed with the `sl` property on the `dbtCloudClient` class (e.g. `client.sl.query`)

Removed

- All of the methods in the `_MetadataClient` except for `query`. The Discovery API no longer allows a user to specify every single field recursively, which is what the `sgqlc` package would do.

Added

- An optional keyword argument `use_beta_endpoint` to the `dbtCloudClient` class. This will default to `True`, which means that the Discovery API will use the beta endpoint at https://metadata.<host>/beta/graphql instead of https://metadata.<host>/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 the `pageInfo` field.

Updated

- Loosen restrictions on Pydantic - ">=2.0,<3.0"

Added

- `retries` argument to the `trigger_job` method. This will allow you to retry a job `retries` amount of times until completion, which is defined as `success` or `cancelled`.

Updated

- `trigger_job_from_failure` method to point at the new `rerun` endpoint. Logic is no longer necessary internally.