v1.2.0rc1

[sdebruyn]

What's Changed

• Automatically provision Azure AD users if enabled by @sdebruyn in Automatically provision Azure AD users if enabled #286

Full Changelog: v1.2.0b2...v1.2.0rc1

v1.2.0 (pre-releases)

Possibly breaking change: connection encryption

For compatibility with MS ODBC Driver 18, the settings Encrypt and TrustServerCertificate are now always added to the connection string.
These are configured with the keys encrypt and trust_cert in your profile.
In previous versions, these settings were only added if they were set to True.

The new version of the MS ODBC Driver sets Encrypt to True by default.
The adapter is following this change and also defaults to True for Encrypt.

The default value for TrustServerConnection remains False as it would be a security risk otherwise.

This means that connections made with this version of the adapter will now have Encrypt=Yes and TrustServerCertificate=No set if you are using the default settings.
You should change the settings encrypt or trust_cert to accommodate for your use case.

Features

• Support for dbt-core 1.2
  • Full support for the new grants config
  • New configuration option in the target: auto_provision_aad_principals - setting this to true will automatically create contained database users linked to Azure AD principals or groups if they don't exist yet when they're being used in grant configs
• Support for MS ODBC Driver 18
• Support automatic retries with new retries setting introduced in core
• The correct owner of a table/view is now visible in generated documentation (and in catalog.json)
• A lot of features of dbt-utils & T-SQL utils are now available out-of-the-box in dbt-core and this adapter. A new release of T-SQL utils will follow.
  • Support for all type_* macros
  • Support for all cross-database macros, except:
  • bool_or
  • listagg will only work in SQL Server 2017 or newer or the cloud versions. The limit_num option is unsupported. DISTINCT cannot be used in the measure.

Fixes

• In some cases the TIMESTAMP would be used as data type instead of DATETIMEOFFSET, fixed that

Chores

• Update adapter testing framework to 1.2.1
• Update pre-commit, tox, pytest and pre-commit hooks
• Type hinting in connection class
• Automated testing with SQL Server 2017, 2019 and 2022
• Automated testing with MS ODBC 17 and MS ODBC 18

---

This discussion was created from the release v1.2.0rc1.