- Added Azure CLI authentication to bridge the gap of local development workflows and let more people use the provider.
- All authentication is completely lazy-initialized, which makes it provider overall more stable.
- Significantly increased unit test coverage, which runs before every merge of a pull request.
- Introduced constantly running integration test suite environments: azsp, azcli & awsmt
- Numerous stability improvements for clusters, mounts, libraries, notebooks, files, authentication and TLS connectivity.
- Added ability to mount storage without explicitly defining a cluster, though it will still launch auto-terminating
terraform-mount
cluster to perform the mount. databricks_cluster
&databricks_job
now share significant portion of configuration wiring code, therefore increasing the stability of codebase.- Added support for Terraform 0.13 local builds for those who develop or cannot wait for next release.
- Added AWS IAM Policy data helpers to simplify new deployments.
- Migrated all documentation to Terraform Registry format, therefore having a single always-accurate place for end-user guides.
- Internally, codebase has been split into multiple packages, which should make further contributions simpler.
Updated dependency versions:
- github.com/Azure/go-autorest/autorest v0.11.4
- github.com/Azure/go-autorest/autorest/adal v0.9.2
- github.com/Azure/go-autorest/autorest/azure/auth v0.5.1
- github.com/aws/aws-sdk-go v1.34.13
- gopkg.in/ini.v1 v1.60.2
Deprecations
library_*
is no longer receiving fixes and will be removed in0.3
, please rewrite cluster & job resources to uselibrary
configuration block.basic_auth
provider block is no longer receiving fixesand will be removed in0.3
, please useusername
andpassword
optionsazure_auth
provider block is no longer receiving fixesand will be removed in0.3
, please useazure_*
options
Behavior changes
- Previously, mounts code paths were different functions. This release unifies them to be a single testable codebase with different configuration options & re-use of the critical code paths. For maintainability reasons, there's no longer check performed on container & storage account names, but rather on high-level mount source uri.