terraform-provider-databricks
terraform-provider-databricks copied to clipboard
Databricks Terraform Provider
## Changes - Renamed `databricks_catalog_workspace_binding` to `databricks_workspace_binding` ## Tests - [x] `make test` run locally - [x] relevant change in `docs/` folder - [x] covered with integration tests in `internal/acceptance`...
the issue is with the user code - this is how you specify multiple libraries. @edwardfeng-db normally, we need to alias plural to singular, i.e. `library` to avoid confusion for...
## Changes - Renamed `databricks_catalog_workspace_binding` to `databricks_workspace_binding` - Added support to set `ISOLATION_MODE` for `databricks_external_location` and `databricks_storage_credential` - Added support for 2 additional `securable_type`: `external-location` and `storage-credential` ## Tests -...
#As per the resource [documents](https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/sql_endpoint#:~:text=0%20to%20disable%20the%20auto%20stop.) setting up the auto_stop_mins to 0 should disable the auto stop but it is set to 10 min. Also, as per the state file, the...
The advanced workspace configuration allows controlling the [Workspace access for Databricks personnel](https://docs.databricks.com/en/admin/workspace/workspace-access.html). It seems this setting is missing in the Terraform provider, and it would be very useful to have...
Bumps [github.com/hashicorp/hcl/v2](https://github.com/hashicorp/hcl) from 2.20.1 to 2.21.0. Release notes Sourced from github.com/hashicorp/hcl/v2's releases. v2.21.0 Enhancements Introduce ParseTraversalPartial, which allows traversals that include the splat ([*]) index operator. (#673) ext/dynblock: Now accepts...
### Use-cases [databricks_mws_permission_assignment](https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/mws_permission_assignment) objects do not detect workspace-wide configuration drift such as additional groups being added to the workspace that are not defined in IAC which would be very useful...
### Configuration ```hcl resource "databricks_automatic_cluster_update_workspace_setting" "auto-patching" { provider = databricks automatic_cluster_update_workspace { enabled = true restart_even_if_no_updates_available = false maintenance_window { week_day_based_schedule { day_of_week = "SUNDAY" frequency = "FIRST_AND_THIRD_OF_MONTH" window_start_time {...
## Changes This PR will resolve https://github.com/databricks/terraform-provider-databricks/issues/3691. - Make the `schedule.pause_status` field read-only. - Remove the description of the field from the documentation. ## Tests - [x] `make test` run...
When a `quality_monitor` resource with the `schedule` field is created, the `terraform plan` command always shows an unexpected change for the `pause_status` read-only field. ### Configuration ```hcl data "databricks_sql_warehouse" "all"...